Repository navigation
Conversation
An API method returns data, encoded as JSON, or a winter.web.Response. The output processors and their registry are gone: register_output_processor_resolver, IOutputProcessor, IOutputProcessorResolver, register_output_processor and winter.django.output_template. A template is rendered by the API method into a Response. Page was the only API processor of Winter, and it needed the request only for the previous and next links of its meta. Those links are dropped, so Page is encoded by a JSON encoder registered for its type, which anyone can write for their own types: winter.json.register_encoder is exported for that. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…handler Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
This branch has not been deployed
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
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.
Stacked on #346.
What
winter.web.Response. Output processors and their registry are gone:register_output_processor_resolver,IOutputProcessor,IOutputProcessorResolver,register_output_processor,winter.django.output_template.Response(HTTPStatus.OK, render_to_string('report.html', context).encode(), {'content-type': 'text/html'}).Pageis encoded by a JSON encoder registered for its type (winter/web/pagination/page_encoder.py). The fields a subclass adds still go tometa.meta.previousandmeta.nextare dropped, together withwinter.web.pagination.utils; the OpenAPI schema ofPageloses them too.winter.json.register_encoderis exported, so the encoder of one's own type is written the same way as Winter's encoder ofPage.Why
Pagewas Winter's only API output processor, and it needed the request only to build the previous and next links. Without the links, aPageis plain data, and everything Winter ships for the response body is built from public pieces. To be confirmed on the consumer: nobody, including clients of its public API, reads the links.🤖 Generated with Claude Code