Make regex validation filter optional#227
Merged
nico-mcalley merged 2 commits intoe-Spirit:masterfrom Sep 22, 2025
Merged
Conversation
Collaborator
|
Hi, the change looks correct and minimal 👍 |
Contributor
Author
|
Hello @jodeleit-es, |
github-actions bot
pushed a commit
that referenced
this pull request
Sep 22, 2025
# [10.24.0](v10.23.0...v10.24.0) (2025-09-22) ### Features * **QueryBuilder:** Make regex validation filter optional ([#227](#227)) ([5937e64](5937e64))
|
🎉 This PR is included in version 10.24.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR allow the user to skip the javascript regex validation for filters. Filters in the ContentAPI are not necessarily compatible with JavaScript Regex. For example
(?i).*example.*works in ContentAPI but not in JavaScript.