Skip to content

Commit 9c88a52

Browse files
merging all conflicts
2 parents 24ef03b + 84a5696 commit 9c88a52

3 files changed

Lines changed: 6 additions & 2 deletions

File tree

src/content/learn/scaling-up-with-reducer-and-context.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -685,7 +685,7 @@ Now you don't need to pass the list of tasks or the event handlers down the tree
685685
</TasksContext>
686686
```
687687

688-
Instead, any component that needs the task list can read it from the `TaskContext`:
688+
Instead, any component that needs the task list can read it from the `TasksContext`:
689689

690690
```js {2}
691691
export default function TaskList() {

src/content/reference/react-dom/client/createRoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ O React exibirá `<App />` na `root` e assumirá o gerenciamento do DOM dentro d
9090
9191
* Se você chamar `render` na mesma root mais de uma vez, o React atualizará o DOM conforme necessário para refletir o último JSX que você passou. O React decidirá quais partes do DOM podem ser reutilizadas e quais precisam ser recriadas por meio de ["combinação"](/learn/preserving-and-resetting-state) com a árvore renderizada anteriormente. Chamar `render` na mesma root novamente é semelhante a chamar a função [`set` (/reference/react/useState#setstate) no componente root: o React evita atualizações desnecessárias do DOM.
9292
93-
* Although rendering is synchronous once it starts, `root.render(...)` is not. This means code after `root.render()` may run before any effects (`useLayoutEffect`, `useEffect`) of that specific render are fired. This is usually fine and rarely needs adjustment. In rare cases where effect timing matters, you can wrap `root.render(...)` in [`flushSync`](https://react.dev/reference/react-dom/client/flushSync) to ensure the initial render runs fully synchronously.
93+
* Although rendering is synchronous once it starts, `root.render(...)` is not. This means code after `root.render()` may run before any effects (`useLayoutEffect`, `useEffect`) of that specific render are fired. This is usually fine and rarely needs adjustment. In rare cases where effect timing matters, you can wrap `root.render(...)` in [`flushSync`](https://react.dev/reference/react-dom/flushSync) to ensure the initial render runs fully synchronously.
9494
9595
```js
9696
const root = createRoot(document.getElementById('root'));

src/content/reference/react/forwardRef.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,11 @@ title: forwardRef
66

77
Em React 19, `forwardRef` não é mais necessário. Passe `ref` como uma prop em vez disso.
88

9+
<<<<<<< HEAD
910
`forwardRef` será descontinuado em uma versão futura. Saiba mais [aqui](/blog/2024/04/25/react-19#ref-as-a-prop).
11+
=======
12+
`forwardRef` will be deprecated in a future release. Learn more [here](/blog/2024/04/25/react-19#ref-as-a-prop).
13+
>>>>>>> 84a56968d92b9a9e9bbac1ca13011e159e815dc1
1014
1115
</Deprecated>
1216

0 commit comments

Comments
 (0)