8000 Document HttpKernel content rendering system · Issue #2129 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

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.

Sign up for GitHub

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

Jump to bottom
Closed
weaverryan opened this issue Jan 13, 2013 · 5 comments
Closed

Document HttpKernel content rendering system #2129

weaverryan opened this issue Jan 13, 2013 · 5 comments
Labels
actionable Clear and specific issues ready for anyone to take them. Stalled

Comments

@weaverryan
Copy link
Member

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.
@weaverryan weaverryan mentioned this issue Jan 13, 2013
Merged
@javiereguiluz
Copy link
Member

Is this issue still relevant? Is the only one left in the super old 2.2 milestone.

@javiereguiluz
Copy link
Member
8000 javiereguiluz commented Oct 11, 2018

We should also document the SSI render that was included in Symfony 2.6 (see #4484).

@javiereguiluz javiereguiluz mentioned this issue Oct 11, 2018
Closed
@javiereguiluz javiereguiluz mentioned this issue Feb 20, 2019
Merged
@wouterj wouterj removed this from the 2.2 milestone Apr 14, 2019
@carsonbot
Copy link
Collaborator

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

@carsonbot
Copy link
Collaborator

Just a quick reminder to make a comment on this. If I don't hear anything I'll close this.

@wouterj
Copy link
Member
wouterj commented Jan 2, 2021

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.

@wouterj wouterj closed this as completed Jan 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
actionable Clear and specific issues ready for anyone to take them. Stalled
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@javiereguiluz @weaverryan @wouterj @carsonbot
0