Nested providers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone.
Please help me with some advice to complete the task.
The desired application structure is as follows:
<divReact>
<NiceModal.Provider>
<pixiReact>
<NiceModal.Provider>
<content/>
</NiceModal.Provider>
</pixiReact>
</NiceModal.Provider>
</divReact>
There are two types of dialog boxes - on PixiReact and in html.
I want to manage them through one manager.
Please tell me how this can be implemented using NiceModal with nested providers, if it is possible, of course.
Thank you!
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 identifies React and nested NiceModal.Provider usage with PixiReact and HTML dialogs, but names no repository files or tests. Start by tracing provider behavior and existing usage examples; done means confirming whether one manager can control both nested dialog trees and documenting the supported approach or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100