An awesome feature / suggestion from your useDialog codes written in Javascript: about react-dialog-hook HOT 3 CLOSED

Okay. I understand. More like headless architecture. that's great!!

from react-dialog-hook.

After analyzing your code, I'd suggest you create a provider on your own and use useDialog as a method to manage the dialog state. We don't want to create an additional layer on top of our library to keep it as much universal as we can. Also, the disadvantage after implementing this code would be limiting users to open only one dialog at a time.

from react-dialog-hook.

@prince272 You proposed passing a component into the opening function and returning it from the hook. We don't want to make our tool depend on components. Lib itself was made only to manage dialog state, not to be responsible for the component and its rendering. I've added context to be optionally used by users so, feel free to update the package if you are using it. Feel free also to review #11 😄

from react-dialog-hook.