Add methods to components to simplify replacing children
Problem to solve
Would be useful to expose simplified ways to replace components within the component tree.
However it is not immediately obvious how these APIs would work wrt some aspects.
Proposal
I originally wrote this PR as a proposal but there was a lot of discussion on the PR about how exactly they should work.
Someone would need to dig into the discussion and figure out the best approach. The actual PR code might or might not be useful at all depending on the chosen requirements.
flame-engine / flame
A Flutter based game engine.
9.2k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too