feat(api): accept available placeholders as json list #884
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
docker compose doesn't want those fields anymore
Instead of multiple fields with the same name (traditional form-data lists), we also accept a JSON list for the available placeholders. This helps reduce the number of fields in the request, which WAF, Django, and possibly other server-side web components don't appreciate.
winged
force-pushed
the
accept_placeholders_json
branch
from
ae615b2 to
88887c4
Compare
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.
Instead of multiple fields with the same name (traditional form-data
lists), we also accept a JSON list for the available placeholders. This
helps reduce the number of fields in the request, which WAF, Django, and
possibly other server-side web components don't appreciate.