wardle / hermes-api Goto Github PK

There is a method to expand expressions that, if the expression is wrong, throws an exception from the expression parser.

In our implementation we allow users to prevalidate expressions, before actually expanding them, which happens when a data query is e valuated, so we can grant expressions used in queries are actually valid.

We can use the same service for the expansion to actually validate the expression, and if there is an exception, then the expression is not valid. Though when the expression is valid, all the expansion work will happen, which is less performant than just parsing the expression. Also, all codes from the expansion are just discarded, because we care only about the expression validity, not the actual expansion.

It would be useful to have an isValid(String expression): boolean method in the API to support this use case, which internally avoids all the expansion processing and just does the parsing.

Thanks!