Closed marksteyn closed 7 years ago
@terinjokes @tajo might be able to provide more background as to why it was removed initially.
Not really. I've never followed this lib. I'm maintaining one that's very similar but much simpler (it doesn't allow different targets/destinations that document.body).
I know this functionality was previous removed, but doing so causes an issue with cf-ui/cf-component-modal, which now fails if you define more than one modal at at a time.
Supporting multiple children seems like the best solution to me, but what were the reasons for its previous removal, and are they still relevant?
I also want to expose the GatewayRegistry to enable integration with our backbone codebase. Since we can't have a single component wrapping all the react code, I want to create a registry provider component to wrap all our react-views which uses a single shared registry.