deprecate array matcher #737
Merged
Conversation
This file contains 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
chris-rock
force-pushed
the
chris-rock/deprecate-array-matcher
branch
from
710517a
to
b3977c4
Compare
chris-rock
force-pushed
the
chris-rock/deprecate-array-matcher
branch
from
b3977c4
to
2ead086
Compare
chris-rock
force-pushed
the
chris-rock/deprecate-array-matcher
branch
from
2ead086
to
f3b41cc
Compare
|
Awesome, thank you @chris-rock !! Let's solve this in 738 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We decided, that we go full steam backwards regarding the array matchers. Therefore we are going to deprecate all array matchers. #738 is collecting the use cases, that InSpec is not able to cover yet.