Don't trigger our own deprecation warning #826
Merged
+3
−3
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.
Description
I was getting a lot of deprecation warnings from inside this gem, but when I tracked them down, they were actually just an internal call, and also deprecated internally. Easy fix :-)
Git.open(".")
can reproduce the issue on 4.0.1:Git.open
callsGit::Base.open
initialize_components
(line 157)Git::Index.new
with a second positional parameterGit::Index
is a straight subclass ofGit::Path
, which warns us about the positional parameterI started to open an issue, and then decided that was silly - this is a trivial fix. (Though I guess I'll need to wait for a gem release to escape the cli noise)
While exercising it, I also noticed that the comments in Rakefile describing how to run individual tests (
bin/test tests/units/test_archive.rb
) were also outdated, and corrected them.