Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TouchUI Coral3 CheckBox in Mulitifield reading/storing values incorrectly #1998

Closed
3 tasks
marto opened this issue Jul 23, 2019 · 0 comments
Closed
3 tasks
Milestone

Comments

@marto
Copy link
Contributor

marto commented Jul 23, 2019

Required Information

  • AEM Version, including Service Packs, Cumulative Fix Packs, etc: AEM v6.4.3
  • ACS AEM Commons Version: 4.2.3-SNAP and 3.x versions
  • Reproducible on Latest? yes

Expected Behavior

In Touch UI, when using a coral3 checkbox inside a mulifield that has been configured to use acs-commons-nested="JSON_STORE", the value of the object is stored in JSON as a "true" or "false" string instead of a boolean primitive. This is incompatible with the classic UI equivalent that stores the values as primitives and causes the loaded value to not be reflected correctly nor storing the value correctly.

Actual Behavior

We expect the value to be loaded correctly (i.e checkbox checked) when the data is:
./myCopositeField = {myCheckbox: true, myOtherField: "blar" }, currently the checkbox is unchecked.

We expect the value to be stored as a boolean and not a string: eg: ./myCopositeField = {myCheckbox: true, myOtherField: "blar" } and not ./myCopositeField = {myCheckbox: "true", myOtherField: "blar" }

Steps to Reproduce

Setup a multifield in touch UI and classic. The checkbox should read and write consistently between both UIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants