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

chore: relative file paths in error messages #456

Merged
merged 2 commits into from
Jun 21, 2024

Conversation

anton-trunov
Copy link
Member

@anton-trunov anton-trunov commented Jun 21, 2024

Closes #406

  • I have updated CHANGELOG.md
  • [ ] I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases I didn't add tests, just checked it works locally and it should be observable in CI in this check's error message. To properly test everything we should fix issue Add cram-like tests for Tact CLI #315
  • I have run all the tests locally and no test failure was reported
  • I have run the linter, formatter and spellchecker
  • I did not do unrelated and/or undiscussed refactorings -- had to rename some errors because of introducing a parse error category

@anton-trunov anton-trunov added this to the v1.4.0 milestone Jun 21, 2024
@anton-trunov anton-trunov self-assigned this Jun 21, 2024
@anton-trunov anton-trunov merged commit e4f1939 into main Jun 21, 2024
3 checks passed
@anton-trunov anton-trunov deleted the relative-paths-in-error-messages branch June 21, 2024 14:42
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.

Use relative paths in compiler messages
1 participant