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.

Sign up for GitHub

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

[EAK-358] Remove all escaping\changing user's value if it does not violate JCR naming rules #358

Open

liubou-masiuk opened this issue Jul 7, 2022 · 1 comment

Labels

Projects

Development tasks

Collaborator

liubou-masiuk commented Jul 7, 2022

As a toolkit user
I want to be able to use any valid JCR name for nodes\attributes without it being escaped by the toolkit.

Example of incorrect behaviour:

add a fieldset with namePrefix ending with a dash (e.g. 'myPrefix-')
observe the result: field names do not have the dash

For the definition of a valid name refer to the implementation of JcrUtil

liubou-masiuk added the AEM label

liubou-masiuk added this to To do in Development tasks via automation

Collaborator

smiakchilo commented Jul 3, 2023

The JCR specification to follow: https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#:~:text=rfc3986%23section%2D3%20*/-,3.2.2%20Local%20Names,-A%20JCR%20local

smiakchilo moved this from To do to In progress in Development tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment