I feel like I may have asked this before but is there a reas

Question

I feel like I may have asked this before but is there a reason why a resource does not expose its name

little-cartoon-10569 · Answer

Probably not a reason per se the name of a resource is the key in a map The value resource object doesn t really need the key

little-cartoon-10569 · Answer

The name is essentially part of the state rather than part of the resource

worried-queen-62794 · Answer

It would be really useful when creating resources based on other resources

little-cartoon-10569 · Answer

In a ComponentResource I just pass the name straight through

little-cartoon-10569 · Answer

Or sometimes append something to it

worried-queen-62794 · Answer

Yes of course that s what I want to do but then you end up having to push this extra parameter around and duplicate it all over the place

worried-queen-62794 · Answer

I ll show you an example one minute

little-cartoon-10569 · Answer

If you re constructing resources outside of the constructor yes you do currently have to do that disappointed Unless maybe you can duck type the name somehow

little-cartoon-10569 · Answer

Yep looks like this might be worth a try if you don t mind sneaking under the covers `const internalName = resource as any name `

worried-queen-62794 · Answer

Oh yeah cool that will do

worried-queen-62794 · Answer

Thanks

little-cartoon-10569 · Answer

Usual caveat may break without warning Undocumented internal code Etc