Skip to content

Conversation

@sebmarkbage
Copy link
Collaborator

This changes the "default" retryTime to NoWork which schedules at Normal pri.

Dehydrated bouundaries normally hydrate at Never priority except when they retry where we accidentally increased them to Normal because Never was used as the default value. This changes it so NoWork is the default.

Dehydrated boundaries however get initialized to Never as the default.

Therefore they now hydrate as Never pri unless their priority gets increased by a forced rerender or selective hydration.

This revealed that erroring at this Never priority can cause an infinite rerender. So I fixed that too.

This changes the "default" retryTime to NoWork which schedules at Normal
pri.

Dehydrated bouundaries normally hydrate at Never priority except when they
retry where we accidentally increased them to Normal because Never was used
as the default value. This changes it so NoWork is the default.

Dehydrated boundaries however get initialized to Never as the default.

Therefore they now hydrate as Never pri unless their priority gets
increased by a forced rerender or selective hydration.

This revealed that erroring at this Never priority can cause an infinite
rerender. So I fixed that too.
@sizebot
Copy link

sizebot commented Oct 16, 2019

No significant bundle size changes to report.

Generated by 🚫 dangerJS against 6e39f06

@sebmarkbage sebmarkbage merged commit 6ff23f2 into facebook:master Oct 16, 2019
acdlite added a commit to acdlite/react that referenced this pull request Oct 16, 2019
Fixes test added in facebook#17105, which was based on an earler commit than the
one that removed the `unstable_` prefix from `createRoot`.
acdlite added a commit that referenced this pull request Oct 16, 2019
Fixes test added in #17105, which was based on an earler commit than the
one that removed the `unstable_` prefix from `createRoot`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants