-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Add future.v7_startTransition flag #10596
Conversation
🦋 Changeset detectedLatest commit: 2eac9cb The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
"react-router": minor | ||
"react-router-dom": minor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is a new future flag it'll be a new 6.13.0 minor release
@@ -49,12 +49,46 @@ The lifecycle is thus either: | |||
|
|||
## Current Future Flags | |||
|
|||
Here's the current future flags in React Router v6 today: | |||
Here's the current future flags in React Router v6 today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this feel confusing? Some flags are router-only and have nothing to do with rendering, others are render-only so I kept them split, but this does mean we export a FutureConfig
from both @remix-run/router
and react-router
.
Move the feature detection stuff to it's own file const START_TRANSITION = "startTransition";
const startTransitionImpl = React[START_TRANSITION];
export default startTransitionImpl || (cb) => cb(); |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Closes #10579 (second half)