-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
[Blazor] API for interpreting RenderFragment contents. #17200
Comments
Cos you give a mock-up example of this, please! Thanks @javiercn |
Related: #29648 |
Seems like this would be possible right now...
I'm aware that frames belong to an internal package, that's not a showstopping problem for me, but it would be nice if Blazor had a legit API that let me do something equivalent to this. |
I recently ran into this problem with - #36976 The way I've fudged it myself so far is to // Add a dummy entry to the destination array in the builder, this increments the count
destbuilder.AddMarkupContent(i, "");
// Do a direct assign to the array to overwrite the struct.
var destframes = destbuilder.GetFrames();
destframes.Array[i] = srcframes.Array[i]; I'm sure this isn't right but for now it does work. Ideally we need an API for copying / assigning an existing frame from a different Array of frames. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
I can see this ticket is swallowing others, and from developer perspective it is a problem, because I fear the scope of this particular issue is so grand it will take more years to accomplish (and this is not set in stone it will ever be). And the swallowed posts are more focused, and I believe more probable to support right now. I am pointing at supporting collection of RenderFragment (currently there are workarounds for it, but AFAIK not proper solutions). So writing this from 2024 perspective, 5 years passed and there is still no basic collection support because it could not be done in this time no matter what, or there is no support because we keep aiming higher and this is what kills collection support? If it the latter case, IMHO it would be much better to split those issues and allow a separate ticket for collection support. |
The idea is to allow interpreting a render fragment so that it can be transformed to change it before applying it.
The text was updated successfully, but these errors were encountered: