Skip to content

Conditionally Rendered Components Cannot Have Context #789

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

Closed
rmorshea opened this issue Jul 13, 2022 · 0 comments · Fixed by #787
Closed

Conditionally Rendered Components Cannot Have Context #789

rmorshea opened this issue Jul 13, 2022 · 0 comments · Fixed by #787
Labels
flag-triage Not prioritized.

Comments

@rmorshea
Copy link
Collaborator

Current Situation

Conditionally rendered components do not have access to contexts. This is because we only make contexts available on the first render which turns out to be a relatively trivial case to solve.

Proposed Actions

To consider this case of conditionally rendered components we must track the contexts which are available to a component in their corresponding hooks as state.

@rmorshea rmorshea added the flag-triage Not prioritized. label Jul 13, 2022
@rmorshea rmorshea changed the title Fix Conditional Renders With Context Conditionally Rendered Components Cannot Have Context Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag-triage Not prioritized.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant