docs: Add skills for deferrable views and server-side rendering - #69947
docs: Add skills for deferrable views and server-side rendering#69947SkyZeroZx wants to merge 1 commit into
Conversation
| - Put specific paths before the `**` fallback. | ||
| - Keep client router paths and server route paths aligned. | ||
| - Use `RenderMode.Prerender` only when the required data is available at build time. | ||
| - Call `inject()` before the first `await` in `getPrerenderParams`. |
There was a problem hiding this comment.
Call
inject()before the firstawaitingetPrerenderParams.
I added this because of how injection/reactive contexts currently work. We should probably add it to the Injection Context skill to explain it better?
There was a problem hiding this comment.
Yes IMO. I feel like I saw an issue that turned into a docs PR mention about this, so I think any relevant skill could use this note as well
There was a problem hiding this comment.
I'll probably move this to another PR with some improvements I could make, along with some things I'd like to add about Angular event binding.
c7b0b3a to
314db44
Compare
314db44 to
9acc0cb
Compare
| @@ -0,0 +1,68 @@ | |||
| # Deferrable Views | |||
|
|
|||
| Use a `@defer` block for content that that can be lazy loading and is not required for the initial render. Angular splits eligible | |||
There was a problem hiding this comment.
Should there be another word or two to specify that this is template content? As opposed to something like injectAsync for lazy loading services being an adjacent idea but not necessarily related to content rendered in the view.
edit: I know the whole page and file name is about views, but idk, maybe an extra word for good measure for this first block
MarkTechson
left a comment
There was a problem hiding this comment.
Getting there! Thanks for opening this up. I think there's a bit more polish needed but it's on the way.
9d41bac to
eb8552f
Compare
No description provided.