Feature/weos 1127 - As a developer I should be able to get a list of content type #103
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
added get api bdd test added bare function for api discovery made fixes to feature file formatting
added ability to set expected content type in the context so it can be checked in the api discovery handler
added test for response type in context
added attach discovery handler test
feature/Weos 1247 - API Discovery
made default endpoints for returning swagger ui as json and html
feature/Weos 1249 - Add handler to allow user to get swagger configuration as html or json
ensure returning json configuration does not redirect
feature/WEOS-1250 - PR Changes
Aidan-E
approved these changes
Feb 21, 2022
akeemphilbert
approved these changes
Feb 21, 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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: