Open
Description
In general, we need to look at every component that we ship and ensure there's a way for them to work on each render mode in a reasonable way across render modes.
- QuickGrid.
- Does not offer a way to work on SSR scenarios. In particular:
- Pagination
- Ordering
- Filtering
- Does not offer a way to work on SSR scenarios. In particular:
- NavLink / Links
- On interactive scenarios you can use
@onclick
to add an event handler to anya
element. - On SSR scenarios it requires using a form. Can we generate such forms in SSR scenarios to allow running logic? (might need to support GET forms)
- On interactive scenarios you can use
- Section(s)
- Better error handling across different render modes.
- Cascading parameters:
- Support explicitly serializing a cascading value across render boundaries.
- Will require that we either are able to serialize the render fragment and render any component as a root component (the cascading value itself would be rendered statically)
- Would be something that would be opt-in at the cascading value declaration