Details
Assignee
Michael OffnerMichael OffnerReporter
David RogersDavid RogersPriority
MinorNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Affects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
David Rogers
David RogersPriority
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Affects versions
Created 10 February 2022 at 18:40
Updated 6 March 2025 at 11:28
Might be hard to change since there is probably code that relies on current Lucee behavior.
Empty arrays are treated incompatibly between Lucee5 and ACF2021, when used as the receiver for `array.every`
<cfscript> a = []; x = a.every((v) => true); y = arrayEvery(a, (v) => true); // lucee – [false, false] // adobe – [true, true] writedump([booleanformat(x),booleanformat(y)]); </cfscript>
Maybe just a curiosity, but as precedent in other languages, JS also has this exact syntax as a member function, and the empty array produces true:
/* javascript */ [].every(v => true) // true