fix: incorrect response schema for discover features #1912
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
Signed-off-by: Daniel Bluhm <[email protected]>
Signed-off-by: Daniel Bluhm <[email protected]>
dbluhm
force-pushed
the
fix/query-features-response-schema
branch
from
1e55e53 to
859d5f5
Compare
Codecov Report
@@ Coverage Diff @@
## main #1912 +/- ##
==========================================
- Coverage 93.67% 93.67% -0.01%
==========================================
Files 539 539
Lines 34145 34143 -2
==========================================
- Hits 31984 31982 -2
Misses 2161 2161 |
andrewwhitehead
approved these changes
Aug 26, 2022
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.
Small change that won't really affect anything but OpenAPI json and client generators.
The query features endpoint returns the discovery record directly rather than nesting it in a
resultsattribute.