Allow configuring the bind/render hooks and media type per route #87
Conversation
This file contains hidden or 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
Being able to configure the bind and render hooks and the media types per route is convenient in order to be able to easily manage API which work with various types of data. I introduced two variables for the media types (request and response) in order to be able to make the distinction in Fizz between the requests and responses media types.
wI2L
approved these changes
Aug 18, 2022
|
mcorbin/fizz@1b8b7d7 depends in this PR to be proposed as a CL on wI2L/fizz. |
|
+1 |
lucasstine-demandiq
added a commit
to Demand-IQ/gadgeto
that referenced
this pull request
May 26, 2023
from main branch on forked repo loopfz#87
|
Is there any movement on this? Having the ability to configure media types per route would be very convenient. @loopfz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Being able to configure the bind and render hooks and the media types
per route is convenient in order to be able to easily manage API which
work with various types of data.
I introduced two variables for the media types (request and response)
in order to be able to make the distinction in Fizz between the
requests and responses media types (I already have a POC
locally for that: wI2L/fizz@9fa8e0b)
Issues in Fizz like this one
should be fixable with what I did.