I was curious if there was a particular reason that the .from shorthand only worked for StateFields and not for other Facets. Here’s an example of a pattern we follow in our codebase:
But .compute([f], (state) => state.facet(f)) feels more verbose than it needs to be (unless, of course, I’m missing a reason it has to be this way). I’m wondering if the same shorthand that is used for state fields could also work for other facets, so I could do:
My thinking is that a facet that just mirrors another facet’s value is not a common enough thing to need a shortcut for. What is the use case you’re doing this for?