Skip to content

Deprecate Prism::Translation::Parser #3526

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Earlopain
Copy link
Contributor

Closes #3524

Either use Prism::Translation::Parser34 or Parser::Translation::ParserCurrent.
It's a remnamt of when prism was only able to parse a single ruby version.

Every method instantiates the parser class, so a deprecation in just initialize is good enough.

In the future this can be cleaned up, currently the autload on the parser class is in the way.

To keep git history intact
@Earlopain Earlopain force-pushed the parser-translator-no-ambiguous-version branch from 2cbf8ed to 43fdf3e Compare March 28, 2025 11:26
@Earlopain Earlopain changed the title Deprecate Prism::Translator::Parser Deprecate Prism::Translation::Parser Mar 28, 2025
Either use `Prism::Translation::Parser34` or `Parser::Translation::ParserCurrent`.
It's a remnamt of when prism was only able to parse a single ruby version.

Every method instantiates the parser class, so a deprecation in `initialize` is good enough.

In the future this can be cleaned up, currently the autload on the parser class is in the way.
@Earlopain Earlopain force-pushed the parser-translator-no-ambiguous-version branch from 43fdf3e to 4318ecc Compare March 28, 2025 11:57
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.

Deprecate Prism::Translation::Parser
1 participant