Skip to content

Fix validation when visual query is swallowed by the SQL part due to parse issues#389

Merged
thomasp85 merged 4 commits intomainfrom
issue256-validate-functional-mapping
Apr 29, 2026
Merged

Fix validation when visual query is swallowed by the SQL part due to parse issues#389
thomasp85 merged 4 commits intomainfrom
issue256-validate-functional-mapping

Conversation

@thomasp85
Copy link
Copy Markdown
Collaborator

Fix #256

@thomasp85 thomasp85 requested a review from teunbrand April 28, 2026 10:10
@teunbrand
Copy link
Copy Markdown
Collaborator

The linked issue had 2 options: A) Allow expressions or B) Catch in validation. But there might be a 3rd option C) which is fiddling with the grammar so the parsing is correct but the contents illegal. It might be worth having Claude explore the option for a bit before we commit to option B.

@thomasp85
Copy link
Copy Markdown
Collaborator Author

that might be possible for the exact issue described there, but when a new parsing issue happens that result in the same we are back at square one. This PR address a real deficiency in how we treat the result of validation which is currently erroneous

Copy link
Copy Markdown
Collaborator

@teunbrand teunbrand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have one concern about a false positive case, if I'm reading the code right

Comment thread src/validate.rs Outdated
@thomasp85 thomasp85 requested a review from teunbrand April 29, 2026 09:49
Copy link
Copy Markdown
Collaborator

@teunbrand teunbrand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thomasp85 thomasp85 merged commit d0872bb into main Apr 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SQL expressions in VISUALISE mappings silently consumed as SQL instead of reporting parse error

2 participants