Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-6454

nodeNameValidator: introduce ability to redefine regular expression

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Neutral
    • 6.2.11
    • 6.2.5
    • None
    • Yes
    • Yes
    • Yes
    • Maintenance 64, Maintenance 65
    • 2

    Description

      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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                aichimescu Andrei Ichimescu
                bfaniuk Boris Faniuk
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - Not Specified
                      Not Specified
                      Logged:
                      Time Spent - 14m
                      14m