Fix #165 #166
Merged
Fix #165 #166
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
zmay2030
force-pushed
the
fix-spec-parser-ignoring-response-entries-with-ext-165
branch
4 times, most recently
from
7f801bf
to
1e545b9
Compare
Signed-off-by: Ahmad Moudani <ahmad.moudani@crowdstrike.com>
zmay2030
force-pushed
the
fix-spec-parser-ignoring-response-entries-with-ext-165
branch
from
1e545b9
to
f85abf4
Compare
casualjim
approved these changes
Apr 21, 2023
zmay2030
deleted the
fix-spec-parser-ignoring-response-entries-with-ext-165
branch
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.
Fixes issue where parser does not hydrate responses' status code entries when there's an extension