-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Move NodePattern into AST namespace #7
Comments
I was about to file the same ticket myself. :D Eventually we should move everything that's under |
It's also a bit weird that |
Looks like a good idea to move Probably best to create the aliases in We could do the same for I think it's a principle to have a common base class for errors. I don't think we need a An alternative solution would be to have |
Forgot to mention, but |
Nevermind, |
👍 Okay, I guess once this is done we can bump |
…bocop/token_spec.rb into ast/ Done in two operations to facilitate git-blame
…bocop/token_spec.rb into ast/ Done in two operations to facilitate git-blame
… related method from rubocop-ast
…essedSource and Token
…essedSource and Token
…bocop/token_spec.rb into ast/ Done in two operations to facilitate git-blame
…oken_spec.rb into ast/ Done in two operations to facilitate git-blame
I'll release 0.0.3 for now... and we can release 1.0 at the same time as rubocop? |
Sounds good. I guess I can now cut one extra RuboCop release to see if we didn't break anything with the extraction for some external gem. |
That's something I want to add to the github actions... testing with earliest compatible rubocop release (not just master) |
Now that we have a separate gem for
rubocop-ast
, maybe it's time we moveNodePattern
out of theRuboCop
namespace and into the gem namespace. WDYT? 🙂The text was updated successfully, but these errors were encountered: