How to deal with a single null value in the array parameter for append()

I see that as well. What I see is that append() does a type cast towards the first array. Means when you have a list of nulls, any value you append will be casted to null.

Thank you stefan.
For me, regarding null safety at least a kind of risk.
Nevertheless I think the chance is not that high, to get just a null value instead of an empty array. 
The question is, if it makes sense to put a lot of effort into it.

Any smooth ideas to avoid this?

Thank you stefan.
For me, regarding null safety at least a kind of risk.
Nevertheless I think the chance is not that high, to get just a null value instead of an empty array. 
The question is, if it makes sense to put a lot of effort into it.

Any smooth ideas to avoid this?

I would use reject() to avoid passing the first one as {null}

For example:

reject(fn!isnull, append({null},{1, 2, 3,4}))

Can you just cast the null to an integer? Doing this worked for me:

append(tointeger({null}),{1,2,3,4})

Hi peter,

I had the same idea yesterday

after a tointeger(null), the result is:

• null(Number (Ganzzahl))
• 1(Number (Ganzzahl))
• 2(Number (Ganzzahl))
• 3(Number (Ganzzahl))
• 4(Number (Ganzzahl))
  

so that confirms stefans suggestion regarding the cast funcitonality towards the first array

Thank you for your input manuell