Resumable Streams
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21k
- Forks
- 6.8k
- PR merge metrics
- No merged PRs in 30d
Description
The current version of the template does not support resumable streams. When the reload button is clicked, the chat is expected to resume from the last step, but this is not happening.
The API route responsible for handling the stream is explicitly returning a 204 status code, it means that the required code has not been implemented.
The image below shows the state of the application after clicking the reload button.
Contributor guide
No contributing guide indexed for this repository
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 at the API route responsible for handling the stream, which currently returns a 204 status code, and trace how the reload button requests the chat state. Done means clicking reload resumes the chat from its last step instead of stopping at the current state; verify the route no longer responds with the unimplemented 204 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- api, backend, stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100