ACF2021 - Case Sensitive structs

Activity

Show:

Zac Spitzer 31 May 2023 at 07:57

Pothys - MitrahSoft 31 May 2023 at 07:16

I created a new ticket.

Michael Offner 30 May 2023 at 14:13

In Luee the following

is a compiler setting and cannot be controlled on runtime level, so if it is set to upper case, all keys are already set to upper case by the compiler.

The only way to overrule that by settings the keys like this animal["SusiSorglos"]=1;, in lucee the “casesensitive“ only controls if the following keys are identical or not

  • susi

  • Susi

to be here compatible with ACF would be a big change.

So for the moment this is not an option as long the community is not asking for it.

 

for “Also ${Aardwolf:"Proteles cristata"} & $[Aardwolf:"Proteles cristata"] syntax is not supported“ please open a separate ticket. this is simply not supported yet.

Pothys - MitrahSoft 10 January 2023 at 10:24

When using structNew("casesensitive") and structNew("ordered-casesensitive") returns the incorrect result and it returns the java class map, not the struct.

Also ${Aardwolf:"Proteles cristata"} & $[Aardwolf:"Proteles cristata"] syntax is not supported in lucee and it throws a failure in D:\........\LDEV3133\test.cfm;Missing [;] or [line feed] after expression error. Seems it works fine in ACF-2021

structNew() with casesensitive in lucee

structNew() with casesensitive in ACF-2021

structNew() with ordered-casesensitive in lucee

structNew() with ordered-casesensitive in ACF-2021

Michael Offner 9 January 2023 at 15:16

can you please be more precise, please do a test case showing the issue.

Fixed

Details

Assignee

Reporter

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

Fix versions

Priority

Created 13 November 2020 at 09:31
Updated 21 May 2024 at 18:59
Resolved 21 May 2024 at 18:59