Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add context to errors #369

Open
agentm opened this issue Mar 3, 2024 · 0 comments
Open

add context to errors #369

agentm opened this issue Mar 3, 2024 · 0 comments
Assignees

Comments

@agentm
Copy link
Owner

agentm commented Mar 3, 2024

Errors from complex Project:M36 expressions are lacking in that it is often difficult to discern what components of the user's expression actually caused the error. Errors should include expression context such as related function/operator name, line number, and line offset.

To achieve this, we need the TutorialD and SQL parsers to propagate line information into the various expressions. Is there a way to achieve this out-of-band so that expressions aren't peppered with context structures? Is that even desireable?

@agentm agentm self-assigned this Mar 3, 2024
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

No branches or pull requests

1 participant