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

Raise a more specific error when encountering an unknown magic comment encoding #999

Conversation

Earlopain
Copy link
Contributor

Closes #998

Let me know if I should tweak the docs for the exception in some way.

I also know that this library still targets Ruby 2.0. CI only seems to test against somewhat recent versions. I used the old begin/end syntax since I know that omitting the begin was added somewhere between but other than that I haven't tested on older versions.

@iliabylich iliabylich merged commit b920c87 into whitequark:master Mar 10, 2024
9 checks passed
@iliabylich
Copy link
Collaborator

Let me know if I should tweak the docs for the exception in some way.

Looks good to me. Thank you very much!

@Earlopain Earlopain deleted the more-specific-error-for-invalid-encoding-comment branch March 10, 2024 16:13
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.

Parsing code with an invalid encoding raises
2 participants