mattermost / mattermost/react-native-network-client
Why exactly single URLSessionConfiguration is bad?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 26
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 2
Description
Were there some exact issues you could not fix using RN fetch api and RN websockets for multiple servers? Could you please point them out?
Thank you.
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
No files, tests, or entry points are named. First clarify which limitation or behavior should be documented regarding a single URLSessionConfiguration versus React Native fetch and WebSockets, then define the expected explanation and its documentation location before starting work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- mobile, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100