支持 useSuspenseData 的 refetch 逻辑
Open
Nobody has claimed this yet.
rfc
- Dominant language
- TypeScript
- Stars
- 18.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
### Summary | 概述
_No response_
### Motivation | 背景
在输出流式数据并完成 hydrate 后，对应 useSuspenseData 不支持 refetch，这样会造成，同一个请求逻辑需要再次写一次 useRequest 逻辑。期望框架提供解决方案或最佳实践。
### Usage example | 使用示例
_No response_
### Detailed design | 方案设计
提供新 API 简化上述逻辑
### Additional context | 额外信息
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the useSuspenseData and useRequest entry points and the hydrate flow described in the issue. Define how refetch should work after streamed data is hydrated, and consider the requested API or best practice; done means the same request logic no longer needs to be duplicated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100