[SHACK-304] Deprecation checking turns up false positive #7515
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
When the location string during a deprecation check looks like
/opt/chefdk/embedded/lib/ruby/gems/2.5.0/gems/chef-14.3.37/spec/unit/chef_class_spec.rb:141:in 'block (4 levels) in <top (required)>'
then trying to silencedeprecation warnings using only an index number (EG,
Chef::Config[:silence_deprecation_warnings] = [0]
) can end up matchingpart of that location string incorrectly. In this case it matched the 0
in the ruby version.
Issues Resolved
SHACK-304
Check List
Signed-off-by: tyler-ball tball@chef.io