Add tsort to rubocop1.0 gemfile to fix deprecation warning#642
Merged
Conversation
Ruby 4.0 extracted tsort from default gems, causing a deprecation warning when running specs against RuboCop 1.0. Adding it explicitly silences the warning, matching the existing base64 and ostruct shims.
Owner
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tsortgem togemfiles/rubocop1.0.gemfileto silence Ruby 4.0 deprecation warningtsortinternally, which was extracted from Ruby's default gems in 4.0base64andostructshims already in that gemfileTest plan
BUNDLE_GEMFILE=gemfiles/rubocop1.0.gemfile bundle exec rspecruns with no deprecation warnings and no new failures