-
Notifications
You must be signed in to change notification settings - Fork 38.4k
Support rendering stream of fragments #33194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Comments
This was referenced Jul 10, 2024
rstoyanchev
added a commit
that referenced
this issue
Jul 24, 2024
rstoyanchev
added a commit
that referenced
this issue
Jul 24, 2024
rstoyanchev
added a commit
that referenced
this issue
Aug 5, 2024
rstoyanchev
added a commit
that referenced
this issue
Aug 8, 2024
rstoyanchev
added a commit
that referenced
this issue
Aug 8, 2024
Thymeleaf has its own special handling for SSE that gets in the way of fragment rendering. This is why we need to set the response content-type before streaming, and then pass text/html to the View for rendering each fragment. See gh-33194
rstoyanchev
added a commit
that referenced
this issue
Aug 8, 2024
rstoyanchev
added a commit
that referenced
this issue
Aug 8, 2024
rstoyanchev
added a commit
that referenced
this issue
Aug 9, 2024
Based on feedback from htmx-spring-boot. It's more generally useful to process those from within DefaultFragmentsRendering rather than in ModelAndViewMethodReturnValueHandler. That way a custom return value handler can create a FragmentsRendering as well and get the same result. See gh-33194
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
In addition to the ability render multiple fragments added in #33162, htmx and turbo also support rendering fragments over SSE and WebSocket. This is issue is to explore such support.
The text was updated successfully, but these errors were encountered: