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

Add callback for rubocop/ast #8789

Merged
merged 1 commit into from Sep 25, 2020
Merged

Conversation

marcandre
Copy link
Contributor

Loading the version first also gives an opportunity for rubocop/ast to react.
Removing handling of rubocop-ast <1.0 in gemspec no longer needed

See also: rubocop/rubocop-ast#123

Loading the version first also gives an opportunity for `rubocop/ast` to react.
Removing handling of rubocop-ast <1.0 in gemspec no longer needed
@marcandre
Copy link
Contributor Author

marcandre commented Sep 24, 2020

@bbatsov sounds ok to you?
I need to make a fix to rubocop-ast for #8765 that affects rubocop before #8787 (not yet released), so ideally we'd merge this PR, release 0.91.2, and then I can merge rubocop/rubocop-ast#123 and rubocop/rubocop-ast#120, and release rubocop-ast, then I'll merge rubocop/rubocop-ast#114 and the new pattern compiler and release that 😅

@@ -8,12 +8,13 @@
require 'forwardable'
require 'regexp_parser'
require 'unicode/display_width/no_string_ext'

require_relative 'rubocop/version'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add a note here that people should touch this. :-)

@bbatsov
Copy link
Collaborator

bbatsov commented Sep 25, 2020

Wow! That's quite the dependency tree! 😆 I'll merge this now and cut 0.91.2.

@bbatsov bbatsov merged commit 0d168dd into rubocop:master Sep 25, 2020
@marcandre marcandre deleted the ast_callback branch September 25, 2020 14:40
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.

None yet

2 participants