route based async atom and auto refreshing

[lili21]

I would like the async atom refresh when navigate between route instead of just reading the outdated value.
maybe we need a better support ( a utils function?) for this case.

[lili21]

can I reset a resolved async atom to initial state? in this way, the next get would trigger the refreshing

[lili21]

just some of them.

[dai-shi]

Hm, my next question is how would you know/tell which some of them should be refreshed.

[lili21]

if we can somehow bind the async atoms to route, I guess we can clear it all based on route navigate.
But IMO provide a utils function and let the users decide when and what to clear would be a good start.

[dai-shi]

Unlike what I thought in #1147 (reply in thread), I think this is router specific issue.
We basically have two options.

1. Declarative. Something like atomWithLocation feature request: add new atom function atomWithLocationQuery #1140
2. Imperative. "clear" imperatively means creating new atoms in jotai, and atomFamily.remove() is one imperative methods. Of course, useEffect + reset is an option too (but not so happy as jotai way).

[dai-shi]

#1147 (comment)

[dai-shi]

One problem is that there's no standard way to subscribe to route change. Related: #1140

[dai-shi]

https://codesandbox.io/s/objective-mccarthy-kx8jvu?file=/src/history.js

This is what I expect to work in a most jotai way. (Declarative)
Unfortunately, it's not working. history doesn't notify the route change... Not sure what's wrong.