Allow to disable input and output class #2393
Merged
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
dunglas
force-pushed
the
false_in_out
branch
from
5b08b24 to
33ad6d4
Compare
soyuka
approved these changes
Dec 19, 2018
|
Good idea! |
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.
This PR allows to set the new
input_classandoutput_classattributes tofalse. It hints API Platform that the corresponding operation(s) will respectively expect an empty input, or will return nothing.This is especially convenient when creating an endpoint that will return nothing. My use case: I create have a
POST /reset-passwordendpoint that sends a token by mail. This endpoint returns202 Acceptedand nothing else.The next step will be to support
input_classandoutput_class(including this new option) in the documentation normalizers.