First Class React Query support

[eyueldk]

I love Eden, so cool so slick... but for production applications I rarely use the client raw, I mostly use it with React Query.

One problem I had with wrapping Eden Treaty or Eden Fetch in a React Query mutation/query is that it doesn't natively throw errors, it returns them as query objects thus requiring me to wrap them and conditionally throw errors for React Query to identify them as Errors.

const query = useQuery({ queryFn: eden.api.something.get }); // this would never have errors because no exception is thrown

I believe it would be fantastic if there was first class support for React Query (maybe an EdenQuery like EdenFetch).

A killer feature would be for users to define query keys in their routes and the React Query client would invalidate accordingly.

That's my 2 cents. Love the library, love the work.

[theoludwig]

I agree that would be awesome to have first class React Query support.

A killer feature would be for users to define query keys in their routes and the React Query client would invalidate accordingly.

We don't even need that? As key could be the route path, HTTP method, and the json stringified input.