Options for "Global" Provider State
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 271
- Forks
- 23
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Hey there 👋
First of all, love the library. This is a super clever solution to handling the interplay between LiveView and React.
As the title suggests, I'm exploring integrating a library that typically sets a React Context and then reads data off of that context in various locations. I'm curious if there is a good pattern for handling a situation like this or if something like that is outside the intended scope.
Thanks!
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
The issue names no file or test; start by reading the library's LiveView/React integration and how React Context is currently handled. Done would require an agreed pattern or supported behavior for global provider state, but the issue does not define an implementation or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, react
- Domain
- frontend, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100