e6f60d2add · samitouri/QOS-React-2

packages/react-dom/src/__tests__/CSSPropertyOperations-test.js

+1 -1

@@ -224,7 +224,7 @@ describe('CSSPropertyOperations', () => {

224 ReactDOM.render(<Comp />, root);

225 });

226

227 - it('should warn about style containing a Infinity value', () => {

227 + it('should warn about style containing an Infinity value', () => {

228 class Comp extends React.Component {

229 static displayName = 'Comp';

230

packages/react-reconciler/src/ReactFiberCompleteWork.new.js

+1 -1

@@ -884,7 +884,7 @@ function completeWork(

884 // Schedule an effect to clear this container at the start of the next commit.

885 // This handles the case of React rendering into a container with previous children.

886 // It's also safe to do for updates too, because current.child would only be null

887 - // if the previous render was null (so the the container would already be empty).

887 + // if the previous render was null (so the container would already be empty).

888 workInProgress.flags |= Snapshot;

889 }

890 }

packages/react-reconciler/src/ReactFiberCompleteWork.old.js

+1 -1

@@ -884,7 +884,7 @@ function completeWork(

884 // Schedule an effect to clear this container at the start of the next commit.

885 // This handles the case of React rendering into a container with previous children.

886 // It's also safe to do for updates too, because current.child would only be null

887 - // if the previous render was null (so the the container would already be empty).

887 + // if the previous render was null (so the container would already be empty).

888 workInProgress.flags |= Snapshot;

889 }

890 }

packages/react-reconciler/src/ReactFiberTreeContext.new.js

+1 -1

@@ -50,7 +50,7 @@

50 // new level with a single slot. You can think of this as a fork with only one

51 // prong, or an array of children with length 1.

52 //

53 -// It's possible for the the size of the sequence to exceed 32 bits, the max

53 +// It's possible for the size of the sequence to exceed 32 bits, the max

54 // size for bitwise operations. When this happens, we make more room by

55 // converting the right part of the id to a string and storing it in an overflow

56 // variable. We use a base 32 string representation, because 32 is the largest

packages/react-reconciler/src/ReactFiberTreeContext.old.js

+1 -1

@@ -50,7 +50,7 @@

50 // new level with a single slot. You can think of this as a fork with only one

51 // prong, or an array of children with length 1.

52 //

53 -// It's possible for the the size of the sequence to exceed 32 bits, the max

53 +// It's possible for the size of the sequence to exceed 32 bits, the max

54 // size for bitwise operations. When this happens, we make more room by

55 // converting the right part of the id to a string and storing it in an overflow

56 // variable. We use a base 32 string representation, because 32 is the largest

packages/react-reconciler/src/ReactFiberWorkLoop.new.js

+1 -1

@@ -1025,7 +1025,7 @@ function finishConcurrentRender(root, exitStatus, lanes) {

1025

1026 function isRenderConsistentWithExternalStores(finishedWork: Fiber): boolean {

1027 // Search the rendered tree for external store reads, and check whether the

1028 - // stores were mutated in a concurrent event. Intentionally using a iterative

1028 + // stores were mutated in a concurrent event. Intentionally using an iterative

1029 // loop instead of recursion so we can exit early.

1030 let node: Fiber = finishedWork;

1031 while (true) {

packages/react-reconciler/src/ReactFiberWorkLoop.old.js

+1 -1

@@ -1025,7 +1025,7 @@ function finishConcurrentRender(root, exitStatus, lanes) {

1025

1026 function isRenderConsistentWithExternalStores(finishedWork: Fiber): boolean {

1027 // Search the rendered tree for external store reads, and check whether the

1028 - // stores were mutated in a concurrent event. Intentionally using a iterative

1028 + // stores were mutated in a concurrent event. Intentionally using an iterative

1029 // loop instead of recursion so we can exit early.

1030 let node: Fiber = finishedWork;

1031 while (true) {

packages/react-server/src/ReactFizzTreeContext.js

+1 -1

@@ -50,7 +50,7 @@

50 // new level with a single slot. You can think of this as a fork with only one

51 // prong, or an array of children with length 1.

52 //

53 -// It's possible for the the size of the sequence to exceed 32 bits, the max

53 +// It's possible for the size of the sequence to exceed 32 bits, the max

54 // size for bitwise operations. When this happens, we make more room by

55 // converting the right part of the id to a string and storing it in an overflow

56 // variable. We use a base 32 string representation, because 32 is the largest

scripts/release/README.md

+1 -1

@@ -21,7 +21,7 @@ A typical release cycle goes like this:

21 1. When a commit is pushed to the React repo, [Circle CI](https://circleci.com/gh/facebook/react/) will build all release bundles and run unit tests against both the source code and the built bundles.

22 2. Each weekday, an automated CI cron job publishes prereleases to the `next` and `experimental` channels, from tip of the main branch.

23 1. You can also [trigger an automated prerelease via the command line](#trigger-an-automated-prerelease), instead of waiting until the next time the cron job runs.

24 - 2. For advanced cases, you can [**manually prepare and publish to the `next` channel**](#publishing-release) using the [`prepare-release-from-ci`](#prepare-release-from-ci) and [`publish`](#publish) scripts; or to the [**`experimental` channel**](#publishing-an-experimental-release) using the the same scripts (but different build artifacts).

24 + 2. For advanced cases, you can [**manually prepare and publish to the `next` channel**](#publishing-release) using the [`prepare-release-from-ci`](#prepare-release-from-ci) and [`publish`](#publish) scripts; or to the [**`experimental` channel**](#publishing-an-experimental-release) using the same scripts (but different build artifacts).

25 3. Finally, a "next" release can be [**promoted to stable**](#publishing-a-stable-release)<sup>1</sup> using the [`prepare-release-from-npm`](#prepare-release-from-npm) and [`publish`](#publish) scripts. (This process is always manual.)

26

27 The high level process of creating releases is [documented below](#process). Individual scripts are documented as well:

fix typos (#22715)