What problem does this solve or what need does it fill?
Hooks, which give users the ability to respond to components being added and removed (in #10756) are really neat: reasonably performant, atomic, hard to mess up.
I'd like to be able to use this for resources as well: see #11426 for an in-engine design where I think this might help simplify the design and make things more robust.
What solution would you like?
Mirror the work in #10756 and #10839 for resources, condensing internal structure to avoid duplication as needed.
What alternative(s) have you considered?
Don't bother implementing this: the truly complex cases (hierarchies, indexes, relations) that motivate hooks and observers for components are less applicable for resources.
Additional context
I'm not 100% sure we should add this, and am very happy to wait and see if there's a real need or desire for this. But users will ask, and I wanted to open a central place for discussion on design/need/implementation.
What problem does this solve or what need does it fill?
Hooks, which give users the ability to respond to components being added and removed (in #10756) are really neat: reasonably performant, atomic, hard to mess up.
I'd like to be able to use this for resources as well: see #11426 for an in-engine design where I think this might help simplify the design and make things more robust.
What solution would you like?
Mirror the work in #10756 and #10839 for resources, condensing internal structure to avoid duplication as needed.
What alternative(s) have you considered?
Don't bother implementing this: the truly complex cases (hierarchies, indexes, relations) that motivate hooks and observers for components are less applicable for resources.
Additional context
I'm not 100% sure we should add this, and am very happy to wait and see if there's a real need or desire for this. But users will ask, and I wanted to open a central place for discussion on design/need/implementation.