Computed properties fire when an action is emitted

I’m attempting to use computed properties to preserve fetch results and createContextStore;

...
getSomething1: computed((state) => fetch("something1", state.date)),
getSomething2: computed((state) => fetch("something2", state.date)),
getSomething3: computed((state) => fetch("something3", state.date)),
...

I’m then consuming only 1 of the computed properties; getSomething1, everything works perfectly until I change the state of ‘date’, then all three getSomething (1, 2, 3) fire off fetches even though I’m only using the first one anywhere.

[onionhammer]

@ctrlplusb I’ve already switched to using react-query to cache results, but I’m definitely open to recommendations on how I can better use easy-peasy to do this stuff 😉

My initial goal was to store the Promise itself in the computed property, so if multiple things await it it will return a precomputed result if it’s already been fetched

[ctrlplusb]

Using react-query sounds like a much better fit for what you were attempting, by way of the code you showed me. 👍