Provide RegExp flags in content fragment models
- October 3, 2024
- 4 replies
- 729 views
| Request for Feature Enhancement (RFE) Summary: |
Provide the ability to specify the flags for RegExp in content fragment models for custom validation regex.
This can be a mulit-select combobox offering the following flags:
stick (screenshot attached, add combobox under custom regex with these options, that would simplify the regex and enable new possibilities) |
| Use-case: |
We have 2500+ clients that we serve using multi-tenancy. We are using content fragments and headless to deliver that content. We have contractual obligations with a major client that requires us to provide a completely white-labelled experience, from logos to copy. This means that there can be no mention of my company name anywhere in the content. Violations carry a $5M fine. |
| Current/Experienced Behavior: |
Today, it is not possible to specify these flags, so handling things such as case sensitivity is unmanageable, and matching patterns across multiple lines is impossible. (screenshot attach of a hacky, unmanageable regex that only works on single lines) |
| Improved/Expected Behavior: | Adding this additional field, and reading it in the new RegExp constructor on the front end will provide the validation necessary to prevent content authors from accidentally creating a violation. (screenshot attached - add second argument toRegExp with flags) |
| Environment Details (AEM version/service pack, any other specifics if applicable): | 2024.9.17964.20240924T170544Z |
| Customer-name/Organization name: | United Health Group |
| Screenshot (if applicable): | |
| Code package (if applicable): |