mirror of
https://github.com/zebrajr/react.git
synced 2025-12-06 12:20:20 +01:00
a4eb2dfa6f
## Overview This PR adds the `ref` prop to `<Fragment>` in `react@canary`. This means this API is ready for final feedback and prepared for a semver stable release. ## What this means Shipping Fragment refs to canary means they have gone through extensive testing in production, we are confident in the stability of the APIs, and we are preparing to release it in a future semver stable version. Libraries and frameworks following the [Canary Workflow](https://react.dev/blog/2023/05/03/react-canaries) should begin implementing and testing these features. ## Why we follow the Canary Workflow To prepare for semver stable, libraries should test canary features like Fragment refs with `react@canary` to confirm compatibility and prepare for the next semver release in a myriad of environments and configurations used throughout the React ecosystem. This provides libraries with ample time to catch any issues we missed before slamming them with problems in the wider semver release. Since these features have already gone through extensive production testing, and we are confident they are stable, frameworks following the [Canary Workflow](https://react.dev/blog/2023/05/03/react-canaries) can also begin adopting canary features like Fragment refs. This adoption is similar to how different Browsers implement new proposed browser features before they are added to the standard. If a frameworks adopts a canary feature, they are committing to stability for their users by ensuring any API changes before a semver stable release are opaque and non-breaking to their users. Apps not using a framework are also free to adopt canary features like Fragment refs as long as they follow the [Canary Workflow](https://react.dev/blog/2023/05/03/react-canaries), but we generally recommend waiting for a semver stable release unless you have the capacity to commit to following along with the canary changes and debugging library compatibility issues. Waiting for semver stable means you're able to benefit from libraries testing and confirming support, and use semver as signal for which version of a library you can use with support of the feature. ## Docs Check out the ["React Labs: View Transitions, Activity, and more"](https://react.dev/blog/2025/04/23/react-labs-view-transitions-activity-and-more#fragment-refs) blog post, and [the new docs for Fragment refs`](https://react.dev/reference/react/Fragment#fragmentinstance) for more info. |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| forks | ||
| assign.js | ||
| binaryToComparableString.js | ||
| CheckStringCoercion.js | ||
| ConsolePatchingDev.js | ||
| DefaultPrepareStackTrace.js | ||
| DefaultPrepareStackTraceV8.js | ||
| enqueueTask.js | ||
| ExecutionEnvironment.js | ||
| formatProdErrorMessage.js | ||
| getComponentNameFromType.js | ||
| getPrototypeOf.js | ||
| hasOwnProperty.js | ||
| isArray.js | ||
| noop.js | ||
| normalizeConsoleFormat.js | ||
| objectIs.js | ||
| package.json | ||
| ReactComponentInfoStack.js | ||
| ReactComponentStackFrame.js | ||
| ReactDOMFragmentRefShared.js | ||
| ReactDOMSharedInternals.js | ||
| ReactElementType.js | ||
| ReactFeatureFlags.js | ||
| ReactFlightPropertyAccess.js | ||
| ReactInstanceMap.js | ||
| ReactIODescription.js | ||
| ReactOwnerStackFrames.js | ||
| ReactOwnerStackReset.js | ||
| ReactPerformanceTrackProperties.js | ||
| ReactSerializationErrors.js | ||
| ReactSharedInternals.js | ||
| ReactSymbols.js | ||
| ReactTypes.js | ||
| ReactVersion.js | ||
| reportGlobalError.js | ||
| shallowEqual.js | ||