Better application/json request support #845
Closed
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
…interfaces.http.IJSONRequest requests.
|
@thet Are you still planning to work on this PR or can we close it? |
|
Closing the PR after a month of no response. |
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.
Mark application/json reqeusts with IJSONRequest.
Very early draft for exploring ideas on supporting application/json requests and possibly other type of requests.
Those requests can than explicitly be adapted to.
Related PRs:
#845
zopefoundation/zope.publisher#53
References the discussion plone.rest and how it intercepts the traversing chain for JSON requests: https://community.plone.org/t/json-application-messaging-in-plone-core/12353