Pasting a full SQL statement appears to parse the WHERE condition and render the appropriate rules in Query Builder.
We do run a validation/cleanup on the rules generated to remove invalid/incomplete rules (see stackblitz example).
We're running into an issue when the SELECT statement contains a matching column name. This then doesn't render the rule correctly for that matching column name.
See 3 example SQL string tests provided at https://stackblitz.com/edit/angular-ivy-quzld2?file=src%2Fapp%2Fapp.component.ts
Run test1 and test2 to see the expected behavior generating the correct rules. Run test3 to see the bug that does not generate the correct rule.
Please advise.
Also, we're curious about our approach to set rules by SQL and then manually validate and re-set rules. Does this look reasonable? Is there a better/alternative approach? Or possibly some cleanup that you guys would do internally to make this step unnecessary?
Thank you!
Luke