support atomWithQuery

[himself65]

No description provided.

[dai-shi]

Is it for "searchParams"?

We have some discussions in #9.
I think atomWithSearch and/or atomWithSearchParam would be nice.

I don't have bandwidth to work on it. Would you or anyone be willing to do?
I think it's better to write an RFC doc first before implementing, because there should be some ideas for API.

[himself65]

I think it's a little different. In next.js, query could be other things. Like /[queryId]/all, the query.queryId is a subpath

[dai-shi]

I see, location path patterns, I'd say. Maybe, atomWithLocationQuery? Open for ideas.

Same applies 👇

I don't have bandwidth to work on it. Would you or anyone be willing to do? I think it's better to write an RFC doc first before implementing, because there should be some ideas for API.

[lveillard]

I'm trying to achieve it this way:
pmndrs/jotai#485 (comment)

[lveillard]

So I was able to run that one with a useMemo in a component, but not as an atom in a separated file. Importing Router generates too many problems.

For instance even if Router is true, Router.isReady can potentially throw an error...

So I did a workaround by creating a component in the _app.tsx that subscribes to router=useRouter() changes and updates an atom on each change. Then i can use that atom everywhere.

I hope there is a way to add atomWithLocationQuery or atomWithRouter somehow!

[dai-shi]

pmndrs/jotai#485 (comment)

Replied there, but maybe we should continue discussion here? Or open a new one.