mattermost / mattermost/react-native-network-client
ApiClient.invalidate resolve promise when session invalidation not yet finished
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 26
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 2
Description
So when you invalidate client and immediately create new one with same url, you reuse the session that will be invalidated after some delay, and all client requests will receive error that session is invalidated.
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 at ApiClient.invalidate and trace how session invalidation is completed when a new client is created for the same URL. Verify that the invalidation promise does not resolve before the delayed session invalidation finishes; done means a new client cannot reuse that session during the invalidation window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100