You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Option group requestComplexity is described as accepting -1 for every property, but allowRegex is a boolean #10870
The description of the requestComplexity option group in src/Options/index.js ends with:
Each property can be set to -1 to disable that specific limit.
The group also contains requestComplexity.allowRegex, which is a boolean option (parsers.booleanParser). Setting it to -1 is rejected by the boolean validation, so the sentence only applies to the numeric limits (includeDepth, includeCount, subqueryDepth, subqueryLimit, queryDepth, graphQLDepth, graphQLFields, batchRequestLimit). The same sentence is replicated in the generated src/Options/Definitions.js and src/Options/docs.js.
Steps to reproduce
Start Parse Server with:
requestComplexity: {allowRegex: -1}
Actual Outcome
Startup fails with the boolean validation error (requestComplexity.allowRegex must be a boolean.), although the option group description says each property can be set to -1.
Expected Outcome
The description is accurate for every property in the group, for example:
Each numeric property can be set to -1 to disable that specific limit.
Changed in src/Options/index.js and regenerated with npm run definitions.
ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
Activity
parse-github-assistant commentedon Nov 5, 2026
🚀 Thanks for opening this issue!
ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.