You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Scott Gray <le...@gmail.com> on 2008/07/18 23:23:38 UTC

MiniLang's first-from-list behaviour

Hi All,

I noticed the <first-from-list> element does nothing if the list is
either null or empty (i.e. the field retains it's current value), I
was expecting that it would set the field to null.  I would like to do
one of two things, either change the behaviour of the element or
document the element so that people are aware of its current
behaviour.

Any opinions on which?

Thanks
Scott

Re: MiniLang's first-from-list behaviour

Posted by Scott Gray <le...@gmail.com>.
Adrian, David, thanks for your input, I've made the relevant change in
rev. 678116

Regards
Scott

2008/7/19 David Jones <jo...@hotwaxmedia.com>:
>
> Well, when you put it that way...
>
> Yes I think we should change the behavior and have it set the value to null if the list is null or empty. That seems totally reasonable.
>
> -David
>
>
> On Sat, 19 Jul 2008 09:23:38 +1200, "Scott Gray" <le...@gmail.com> wrote:
>> Hi All,
>>
>> I noticed the <first-from-list> element does nothing if the list is
>> either null or empty (i.e. the field retains it's current value), I
>> was expecting that it would set the field to null.  I would like to do
>> one of two things, either change the behaviour of the element or
>> document the element so that people are aware of its current
>> behaviour.
>>
>> Any opinions on which?
>>
>> Thanks
>> Scott
>
>

Re: MiniLang's first-from-list behaviour

Posted by David Jones <jo...@hotwaxmedia.com>.
Well, when you put it that way...

Yes I think we should change the behavior and have it set the value to null if the list is null or empty. That seems totally reasonable.

-David


On Sat, 19 Jul 2008 09:23:38 +1200, "Scott Gray" <le...@gmail.com> wrote:
> Hi All,
> 
> I noticed the <first-from-list> element does nothing if the list is
> either null or empty (i.e. the field retains it's current value), I
> was expecting that it would set the field to null.  I would like to do
> one of two things, either change the behaviour of the element or
> document the element so that people are aware of its current
> behaviour.
> 
> Any opinions on which?
> 
> Thanks
> Scott

Re: MiniLang's first-from-list behaviour

Posted by Adrian Crum <ad...@hlmksw.com>.
It seems to me it should return an empty field.

-Adrian

Scott Gray wrote:
> Hi All,
> 
> I noticed the <first-from-list> element does nothing if the list is
> either null or empty (i.e. the field retains it's current value), I
> was expecting that it would set the field to null.  I would like to do
> one of two things, either change the behaviour of the element or
> document the element so that people are aware of its current
> behaviour.
> 
> Any opinions on which?
> 
> Thanks
> Scott
>