feat: improve error messages for comment assertion parsing #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add line number information to error messages - Provide clearer error messages when trying to add assertions to declarations - Include context about what went wrong and how to fix it - Add try-catch error handling with line number information for parsing errors Fixes #45 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Add test for FunctionDeclaration with assertion comment - Add test for ClassDeclaration with assertion comment - Add test for ImportDeclaration with assertion comment - Ensure all declaration types are properly validated with line numbers 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves error messages for comment assertion parsing to address issue #45.
Changes Made
Before
After
Additional Improvements
Error at line 3: Unexpected token, expected "," (1:9)Test Coverage
Added comprehensive test case to verify the improved error message format includes:
Breaking Changes
None - this only improves error messages without changing functionality.
Related Issues
Fixes #45
🤖 Generated with Claude Code