Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Render CalendarRoot in the same virtualDOM tree to make contexts available #7657

Open
2 tasks done
Amnesthesia opened this issue Apr 17, 2024 · 0 comments
Open
2 tasks done

Comments

@Amnesthesia
Copy link

Checklist

  • I've already searched through existing tickets
  • Other people will find this feature useful

Is this feature for a specific connector (React/Angular/etc)?

React

Feature Description

We've been mostly using FullCalendar with React, but tried to switch React out to use Preact instead. When switching to Preact, our Calendar completely broke because we render events using eventContent that return React components which consume contexts.

All these events become rendered in CalendarRoot, in a separate virtualDOM tree than the main one, and so no contexts are available - which means navigating with useNavigate from react-router, or even accessing Apollo, becomes impossible

There's no option to change this behaviour, or have FullCalendar render in the same tree, as far as I can tell.

It would be great if we were able to render FullCalendar in the same tree and access contexts within eventContent, or at the very least inject other providers wrapping FullCalendar to make them accessible

@acerix acerix changed the title Preact renders FullCalendar in separate tree, with no option to change this, making contexts unavailable Render CalendarRoot in the same virtualDOM tree to make contexts available May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants