trilogy-data / trilogy-data/pytrilogy
Better Parsing Errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 3
- Avg merge
- 7h 18m
- Merged PRs (30d)
- 43
Description
Problem Statement
Improve parsing errors beyond the current wrappers around lark.
This issue is vague, but let's take Rust errors as an inspiration.
Proposed Solution
Add better error messages.
- General wrapper for syntax errors, hide underlying Lark Exception
- Specific error handling for certain failures
-- [ ]select 1;<- missing aliases should have a better error, etc
Alternatives Considered
Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.
Additional Context
Please provide any other information that may be relevant.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the current parser and its wrappers around Lark exceptions, then review the proposed missing-alias case and the Rust error example. Done would require an agreed error design, general syntax-error handling, and specific messages for identified failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100