Laura Schanno
Laura Schanno
@jstewart-shield understood, thank you for the clarification.
Follow-up question for @ivakegg and @jstewart-shield, should any of these validation criteria also apply to fields given via query parameters, or just the query itself?
@jstewart-shield understood, thanks.
A couple of additional questions for @ivakegg and @jstewart-shield: 1. Should #13 apply to regex patterns for any non-regex reserved special characters? Specifically, should we check if any special character...
@jstewart-shield 1. No problem, will do. 2. The parser is indeed run as part of the call. I will add support for returning better error messages for the invalid function.
@ivakegg @jstewart-shield for #10, do we still want to flag cases for escaped wildcards inside of phrases, such as `FIELD:"abc\*def"`, or is this considered valid?
See below for examples on how the parser handles the LUCENE to JEXL conversion with wildcards: - Wildcard inside quoted phrase: `FIELD:"abc*dec"` -> `FIELD == 'abc*dec'` - Escaped wildcard inside...
Understood, will do.
@jstewart-shield understood, I'll factor that into the rule logic.
@jstewart-shield I have created PR #2645 for this. The PR description body contains samples of the messages for the validation rules, as well as the schema of the expected REST...