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.

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

Jump to bottom

[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
Open

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

liubou-masiuk opened this issue Jul 7, 2022 · 1 comment
Assignees
@smiakchilo
Labels
AEM AEM-specific competencies are involved

Comments

@liubou-masiuk
Copy link
Collaborator

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:

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

For the definition of a valid name refer to the implementation of JcrUtil
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smiakchilo smiakchilo

Labels
AEM AEM-specific competencies are involved
Projects
EToolbox Authoring Kit Dev Tasks
Status: In progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smiakchilo @liubou-masiuk