microsoft / microsoft/BotFramework-DirectLineJS
Revisit resume/end/error/expired conversation stories
Open
Nobody has claimed this yet.
approved
P0
triaged
- Dominant language
- TypeScript
- Stars
- 199
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
Note to investigator
Find out all permutations of the resume/end/error/expired over REST API and Web Socket.
Related issues
- #118 Resume conversation after calling
botConnection.end() - #101 "Token expired" signal is not fired on Web Socket route
- #103 Generate a new token using existing conversation ID
- #94 End conversation does not really stop the polling or Web Socket
- #90 Backoff stories
- HTTP 429/400 - we will back off
- HTTP 404 - fatal, we will stop
- #75 End conversation does not really stop Web Socket
- #9 Resume conversation and how to renew expired token
- https://github.com/Microsoft/BotFramework-WebChat/pull/1880 Wiring up for reconnect UI
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 reviewing the REST and Web Socket behavior described in this issue and the related issues #118, #101, #103, #94, #90, #75, and #9. Map the resume, end, error, and expired-token permutations, then define the expected behavior for each path before identifying the affected client entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100