Open javiercn opened 12 months ago
Thanks for contacting us.
We're moving this issue to the .NET 9 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
Thanks for contacting us.
We're moving this issue to the .NET 9 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
This is a common point of confusion for customers, so we could add a new
SerializableCascadingValue
component or similar that is able to flow across component boundaries.With the requirement that the value needs to be JSON serializable and that you won't (probably) get updates (it's a 1-time thing, but maybe we can update via enhanced navigations).
The internal component we use for the render boundary can capture the serializable value providers in the hierarchy, serialize those, and expose them once it begins rendering interactively.