-
Improvement
-
Resolution: Fixed
-
Neutral
-
6.2.5
-
None
-
-
Yes
-
Empty show more show less
-
Yes
-
Yes
-
Maintenance 64, Maintenance 65
-
2
Currently pattern for node name validation is hard coded and just checks for non-empty value. This validation never really works as empty page name will result in "field is required" validation to be fired.
What would make more sense is to catch unwanted symbols here (as anyway they will replaced by dash in nodeNameHelper.getValidatedName and that is unpredictable for editor).
In addition we would like to catch uppercase symbols as they cause issues in Linux environment.
I would propose to introduce pattern and errorMessage parameters that would allow us to define this pattern and avoid having 2 regexp validations for page name.
- is related to
-
MGNLUI-6455 nodeNameValidator doesn't work correctly in "createPage" case
- Closed
- to be documented by
-
MGNLUI-6794 DOC: 'pattern' property also used in 'nodeNameValidator'
- Closed