-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Document HttpKernel content rendering system #2129
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
Comments
Is this issue still relevant? Is the only one left in the super old 2.2 milestone. |
We should also document the SSI render that was included in Symfony 2.6 (see #4484). |
Thank you for this issue. |
Just a quick reminder to make a comment on this. If I don't hear anything I'll close this. |
Let's close here. It's true that we do a bad job in listing all available options and their advantages/disadvantages, but it does seem like we did document all features (ESI, SSI, Hinclude, sub-requests). This probably needs to be fixed by merging all smaller articles into one guide (e.g. the HTTP Cache guide). Anyway, nobody appears to be interested in doing so in the past 7 years, so I don't think it's needed to keep this issue open. |
See #2121
For the "render" changes in 2.2, we've updated the existing documentation. But the rendering system - including the different strategies and their options - should be documented in some central location. My vote would be a small document inside the HttpKernel component docs. If we need something framework-specific in addition to this, I think it will become obvious.
The text was updated successfully, but these errors were encountered: