[Feature]: Deprecate QueryErrorBoundary?

[manudeli]

Package Scope

@suspensive/react-query

Description

// optional-peer-dep:__vite-optional-peer-dep:@suspensive/react:@suspensive/react-query-4
throw new Error(`Could not resolve "@suspensive/react" imported by "@suspensive/react-query-4". Is it installed?`);

Due to the peerDep issue of @suspensive/react-query, some projects have the problem of having to install @suspensive/react. The implementation of QueryErrorBoundary is simple and leaving this implementation up to the user seems to end these problems and solve the peerDep problem.

@gwansikk I want to talk about this issue

Possible Solution

No response

etc.

No response

[coauthors]

People can be co-author:

Candidate	Reasons	Count	Add this as commit message
@manudeli	#1325 (comment) #1325	2	Co-authored-by: manudeli <[email protected]>
@gwansikk	#1325 (comment)	1	Co-authored-by: gwansikk <[email protected]>

[gwansikk]

The implementation of QueryErrorBoundary is simple and leaving this implementation up to the user seems to end these problems and solve the peerDep problem.

I agree. A QueryErrorBoundary can be easily created by the user, and I believe it should be up to the user’s discretion as needed.

How about deprecating it and simply providing guidance in the form of a recipe? For example, a guide explaining how users can combine @suspensive/react-query with @suspensive/react. (This is just a suggestion.)

like Jotai RECIPES: https://jotai.org/docs/recipes/large-objects

[manudeli]

Let's do this in v3