From 2e144716aa0fcdb7554c7acf41f6900c17837046 Mon Sep 17 00:00:00 2001 From: Tina Pu Date: Sat, 8 Jan 2022 11:59:20 -0500 Subject: [PATCH 1/3] Update scaling-up-with-reducer-and-context.md --- .../scaling-up-with-reducer-and-context.md | 113 +++++++++--------- 1 file changed, 56 insertions(+), 57 deletions(-) diff --git a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md index 2bc0877c3d..a2af8deb02 100644 --- a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md +++ b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md @@ -1,24 +1,24 @@ --- -title: Scaling Up with Reducer and Context +title: 使用 Reducer 和 Context 来拓展你的应用 --- -Reducers let you consolidate a component's state update logic. Context lets you pass information deep down to other components. You can combine reducers and context together to manage state of a complex screen. +Reducer 可以整合组件的状态更新逻辑。Context 可以将信息深入传递给其他组件。你可以组合使用它们来共同管理一个复杂页面的状态。 -* How to combine a reducer with context -* How to avoid passing state and dispatch through props -* How to keep context and state logic in a separate file +* 如何结合使用 reducer 和 context +* 如何去避免通过 props 传递 state 和 dispatch +* 如何将 context 和状态逻辑保存在一个单独的文件中 -## Combining a reducer with context {/*combining-a-reducer-with-context*/} +## 结合使用 reducer 和 context {/*combining-a-reducer-with-context*/} -In this example from [the introduction to reducers](/learn/extracting-state-logic-into-a-reducer), the state is managed by a reducer. The reducer function contains all of the state update logic and is declared at the bottom of this file: +在 [reducer 介绍](/learn/extracting-state-logic-into-a-reducer) 的例子里面，状态被 reducer 所管理。reducer 函数包含了所有的状态更新逻辑并在此文件的底部声明： @@ -207,9 +207,9 @@ ul, li { margin: 0; padding: 0; } -A reducer helps keep the event handlers short and concise. However, as your app grows, you might run into another difficulty. **Currently, the `tasks` state and the `dispatch` function are only available in the top-level `TaskBoard` component.** To let other components read the list of tasks or change it, you have to explicitly [pass down](/learn/passing-props-to-a-component) the current state and the event handlers that change it as props. +Reducer 有助于保持事件处理程序的简短明了。但随着应用规模越来越庞大，你就可能会遇到别的困难。 **目前，`tasks` 状态和 `dispatch` 函数仅在顶级 `TaskBoard` 组件中可用。** 若要让其他组件读取 `tasks` 状态或对其进行更改，必须以 props 的形式显式 [传递](/learn/passing-props-to-a-component) 它。 -For example, `TaskBoard` passes a list of tasks and the event handlers to `TaskList`: +例如，`TaskBoard` 将 `tasks` 和事件处理程序传递给 `TaskList`： ```js ``` -And `TaskList` passes the event handlers to `Task`: +`TaskList` 将事件处理程序传递给 `Task`： ```js ``` -In a small example like this, this works well, but if you have tens or hundreds of components in the middle, passing down all state and functions can be quite frustrating! +在像这样的小示例里这样做没什么问题，但是如果你有成千上百个组件，传递所有状态和函数就会让你非常烦恼！ -This is why, as an alternative to passing them through props, you might want to put both the `tasks` state and the `dispatch` function [into context](/learn/passing-data-deeply-with-context). **This way, any component below `TaskBoard` in the tree can read the tasks and dispatch actions without the repetitive "prop drilling".** +这就是为什么，比起通过 props 传递它们，你可能想把 `tasks` 状态和 `dispatch` 函数都 [放入 context](/learn/passing-data-deeply-with-context)。**这样，所有的在 `TaskBoard` 组件树之下的组件都不必一直往下传 props 而可以直接读取 tasks 和 dispatch 函数。** -Here is how you can combine a reducer with context: +下面将介绍如何结合使用 reducer 和 context： -1. **Create** the context. -2. **Put** state and dispatch into context. -3. **Use** context anywhere in the tree. +1. **创建** context。 +2. 将 state 和 dispatch **放入** context。 +3. 在组件树的任何地方 **使用** context。 -### Step 1: Create the context {/*step-1-create-the-context*/} +### 第一步: 创建 context {/*step-1-create-the-context*/} -The `useReducer` Hook returns the current `tasks` and the `dispatch` function that lets you update them: +`useReducer` 返回当前的 `tasks` 和 `dispatch` 函数来让你更新它们： ```js const [tasks, dispatch] = useReducer(tasksReducer, initialTasks); ``` -To pass them down the tree, you will [create](/learn/passing-data-deeply-with-context#step-2-use-the-context) two separate contexts: +为了将它们从组件树往下传，你将 [创建](/learn/passing-data-deeply-with-context#step-2-use-the-context) 两个不同的 context： -- `TasksContext` provides the current list of tasks. -- `TasksDispatchContext` provides the function that lets components dispatch actions. +- `TasksContext` 提供当前的 tasks 列表。 +- `TasksDispatchContext` 提供了一个函数可以让组件分发动作。 -Export them from a separate file so that you can later import them from other files: +将它们从单独的文件导出，以便以后可以从其他文件导入它们： @@ -452,11 +452,11 @@ ul, li { margin: 0; padding: 0; } -Here, you're passing `null` as the default value to both contexts. The actual values will be provided by the `TaskBoard` component. +在这里，你把 `null` 作为默认值传递给两个 context。实际值是由 `TaskBoard` 组件提供的。 -### Step 2: Put state and dispatch into context {/*step-2-put-state-and-dispatch-into-context*/} +### 第二步: 将 state 和 dispatch 函数 放入 context {/*step-2-put-state-and-dispatch-into-context*/} -Now you can import both contexts in your `TaskBoard` component. Take the `tasks` and `dispatch` returned by `useReducer()` and [provide them](/learn/passing-data-deeply-with-context#step-3-provide-the-context) to the entire tree below: +现在，你可以将所有的 context 导入 `TaskBoard` 组件。获取 `useReducer()` 返回的 `tasks` 和 `dispatch` 并将它们 [提供](/learn/passing-data-deeply-with-context#step-3-provide-the-context) 给整个组件树： ```js {4,7-8} import { TasksContext, TasksDispatchContext } from './TasksContext.js'; @@ -474,7 +474,7 @@ export default function TaskBoard() { } ``` -For now, you pass the information both via props and in context: +现在，你可以同时通过 props 和 context 传递信息： @@ -673,11 +673,11 @@ ul, li { margin: 0; padding: 0; } -In the next step, you will remove prop passing. +在下一步中，你将删除通过 props 传递的代码。 -### Step 3: Use context anywhere in the tree {/*step-3-use-context-anywhere-in-the-tree*/} +### Step 3: 在组件树中的任何地方使用 context {/*step-3-use-context-anywhere-in-the-tree*/} -Now you don't need to pass the list of tasks or the event handlers down the tree: +现在你不需要将 tasks 和事件处理程序在组件树中传递： ```js {4-5} @@ -689,7 +689,7 @@ Now you don't need to pass the list of tasks or the event handlers down the tree ``` -Instead, any component that needs the task list can read it from the `TaskContext`: +相反，任何需要 tasks 的组件都可以从 `TaskContext` 中读取它： ```js {2} export default function TaskList() { @@ -697,7 +697,7 @@ export default function TaskList() { // ... ``` -To update the task list, any component can read the `dispatch` function from context and call it: +任何组件都可以从 context 中读取 `dispatch` 函数并调用它，从而更新任务列表： ```js {3,9-13} export default function AddTask({ onAddTask }) { @@ -717,7 +717,7 @@ export default function AddTask({ onAddTask }) { // ... ``` -**The `TaskBoard` component does not pass any event handlers down, and the `TaskList` does not pass any event handlers to the `Task` component either.** Each component reads the context that it needs: +**`TaskBoard` 组件不会向下传递任何事件处理程序， `TaskList` 也不会。** 每个组件都会读取它需要的 context： @@ -901,11 +901,11 @@ ul, li { margin: 0; padding: 0; } -**The state still "lives" in the top-level `TaskBoard` component, managed with `useReducer`.** But its `tasks` and `dispatch` are now available to every component below in the tree by importing and using these contexts. +**state 仍然"存在于"顶层 `TaskBoard` 组件中，由 `useReducer` 进行管理。** 不过，组件树里的组件只要导入这些 context 之后就可以获取 `tasks` 和 `dispatch`。 -## Moving all wiring into a single file {/*moving-all-wiring-into-a-single-file*/} +## 将相关逻辑迁移到一个文件当中 {/*moving-all-wiring-into-a-single-file*/} -You don't have to do this, but you could further declutter the components by moving both reducer and context into a single file. Currently, `TasksContext.js` contains only two context declarations: +这不是必须的，但你可以通过将 reducer 和 context 移动到单个文件中来进一步整理组件。目前，“TasksContext.js” 仅包含两个 context 声明： ```js import { createContext } from 'react'; @@ -914,11 +914,11 @@ export const TasksContext = createContext(null); export const TasksDispatchContext = createContext(null); ``` -This file is about to get crowded! You'll move the reducer into that same file. Then you'll declare a new `TasksProvider` component in the same file. This component will tie all the pieces together: +来给这个文件添加更多代码！将 reducer 移动到此文件中，然后声明一个新的 `TasksProvider` 组件。此组件将所有部分连接在一起： -1. It will manage the state with a reducer. -2. It will provide both contexts to components below. -3. It will [take `children` as a prop](/learn/passing-props-to-a-component#passing-jsx-as-children) so you can pass JSX to it. +1. 它将管理 reducer 的状态。 +2. 它将提供现有的 context 给组件树。 +3. 它将 [把 `children` 作为 prop](/learn/passing-props-to-a-component#passing-jsx-as-children)，所以你可以传递 JSX。 ```js export function TasksProvider({ children }) { @@ -934,7 +934,7 @@ export function TasksProvider({ children }) { } ``` -**This removes all the complexity and wiring from your `TaskBoard` component:** +**这将使 TaskBoard 组件更加直观：** @@ -1125,7 +1125,7 @@ ul, li { margin: 0; padding: 0; } -You can also export functions that _use_ the context from `TasksContext.js`: +你也可以从 `TasksContext.js` 中导出使用 context 的函数： ```js export function useTasks() { @@ -1137,14 +1137,14 @@ export function useTasksDispatch() { } ``` -When a component needs to read context, it can do it through these functions: +组件可以通过以下函数读取 context： ```js {5-7} const tasks = useTasks(); const dispatch = useTasksDispatch(); ``` -This doesn't change the behavior in any way, but it lets you later split these contexts further or add some logic to these functions. **Now all of the context and reducer wiring is in `TasksContext.js`. This keeps the components clean and uncluttered, focused on what they display rather than where they get the data:** +这不会改变任何行为，但它会允许你之后进一步分割这些 context 或向这些函数添加一些逻辑。**现在所有的 context 和 reducer 连接部分都在 `TasksContext.js` 中。这保持了组件的干净和整洁，让我们专注于它们显示的内容，而不是它们从哪里获得数据：** @@ -1172,7 +1172,7 @@ const TasksContext = createContext(null); const TasksDispatchContext = createContext(null); export function TasksProvider({ children }) { - const [tasks, dispatch] = useReducer( + const [tasks, ßdispatch] = useReducer( tasksReducer, initialTasks ); @@ -1344,23 +1344,22 @@ ul, li { margin: 0; padding: 0; } -You can think of `TasksProvider` as a part of the screen that knows how to deal with tasks, `useTasks` as a way to read them, and `useTasksDispatch` as a way to update them from any component below in the tree. +你可以将 `TasksProvider` 视为页面的一部分，它知道如何处理 tasks。`useTasks` 用来读取它们，`useTasksDispatch` 用来从组件树下的任何组件更新它们。 -> Functions like `useTasks` and `useTasksDispatch` are called **[Custom Hooks](/learn/reusing-logic-with-custom-hooks).** Your function is considered a custom Hook if its name starts with `use`. This lets you use other Hooks, like `useContext`, inside it. +> 像 `useTasks` 和 `useTasksDispatch` 这样的函数被称为 **[自定义 Hook](/learn/reusing-logic-with-custom-hooks)。** 如果你的函数名以 `use` 开头，它就被认为是一个自定义 Hook。这让你可以使用其他 Hook，比如 `useContext`。 -As your app grows, you may have many context-reducer pairs like this. This is a powerful way to scale your app and [lift state up](/learn/sharing-state-between-components) without too much work whenever you want to access the data deep in the tree. +随着应用的增长，你可能会有许多这样的 context 和 reducer 的组合。这是一种强大的拓展应用并 [提升状态](/learn/sharing-state-between-components) 的方式，让你在组件树深处访问数据时无需进行太多工作。 -- You can combine reducer with context to let any component read and update state above it. -- To provide state and the dispatch function to components below: - 1. Create two contexts (for state and for dispatch functions). - 2. Provide both contexts from the component that uses the reducer. - 3. Use either context from components that need to read them. -- You can further declutter the components by moving all wiring into one file. - - You can export a component like `TasksProvider` that provides context. - - You can also export custom Hooks like `useTasks` and `useTasksDispatch` to read it. -- You can have many context-reducer pairs like this in your app. +- 你可以将 reducer 与 context 相结合，让任何组件读取和更新它的状态。 +- 为子组件提供 state 和 dispatch 函数： + 1. 创建两个 context (一个用于 state,一个用于 dispatch 函数)。 + 2. 让组件的 context 使用 reducer。 + 3. 使用组件中需要读取的 context。 +- 你可以通过将所有传递信息的代码移动到单个文件中来进一步整理组件。 + - 你可以导出一个像 `TasksProvider` 可以提供 context 的组件。 + - 你也可以导出像 `useTasks` 和 `useTasksDispatch` 这样的自定义 Hook。 +- 你可以在你的应用程序中大量使用 context 和 reducer 的组合。 - From d26db4a6a8dd7dc4240340ebcf16e891f3def299 Mon Sep 17 00:00:00 2001 From: Tina Pu Date: Sat, 8 Jan 2022 12:10:19 -0500 Subject: [PATCH 2/3] Update scaling-up-with-reducer-and-context.md --- .../pages/learn/scaling-up-with-reducer-and-context.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md index a2af8deb02..3bd5a25af0 100644 --- a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md +++ b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md @@ -229,11 +229,11 @@ Reducer 有助于保持事件处理程序的简短明了。但随着应用规模 /> ``` -在像这样的小示例里这样做没什么问题，但是如果你有成千上百个组件，传递所有状态和函数就会让你非常烦恼！ +在像这样的小示例里这样做没什么问题，但是如果你有成千上百个组件，传递所有状态和函数可能会非常麻烦！ -这就是为什么，比起通过 props 传递它们，你可能想把 `tasks` 状态和 `dispatch` 函数都 [放入 context](/learn/passing-data-deeply-with-context)。**这样，所有的在 `TaskBoard` 组件树之下的组件都不必一直往下传 props 而可以直接读取 tasks 和 dispatch 函数。** +这就是为什么，比起通过 props 传递它们，你可能会想把 `tasks` 状态和 `dispatch` 函数都 [放入 context](/learn/passing-data-deeply-with-context)。**这样，所有的在 `TaskBoard` 组件树之下的组件都不必重复往下传 props 而可以直接读取 tasks 和 dispatch 函数。** @@ -251,10 +251,10 @@ Reducer 有助于保持事件处理程序的简短明了。但随着应用规模 const [tasks, dispatch] = useReducer(tasksReducer, initialTasks); ``` -为了将它们从组件树往下传，你将 [创建](/learn/passing-data-deeply-with-context#step-2-use-the-context) 两个不同的 context： +为了将它们从组件树往下传，你将 [创建](/learn/passing-data-deeply-with-context#step-2-use-the-context) 两个独立的 context： - `TasksContext` 提供当前的 tasks 列表。 -- `TasksDispatchContext` 提供了一个函数可以让组件分发动作。 +- `TasksDispatchContext` 提供了一个函数，以便让组件分发动作。 将它们从单独的文件导出，以便以后可以从其他文件导入它们： @@ -1358,7 +1358,7 @@ ul, li { margin: 0; padding: 0; } 2. 让组件的 context 使用 reducer。 3. 使用组件中需要读取的 context。 - 你可以通过将所有传递信息的代码移动到单个文件中来进一步整理组件。 - - 你可以导出一个像 `TasksProvider` 可以提供 context 的组件。 + - 你可以导出一个例如 `TasksProvider` 这样可以提供 context 的组件。 - 你也可以导出像 `useTasks` 和 `useTasksDispatch` 这样的自定义 Hook。 - 你可以在你的应用程序中大量使用 context 和 reducer 的组合。 From 18b729bcc2e2766a1876b65c22bf30260fef721a Mon Sep 17 00:00:00 2001 From: KnowsCount Date: Tue, 11 Jan 2022 16:44:49 +0800 Subject: [PATCH 3/3] fix: space issue --- beta/src/pages/learn/scaling-up-with-reducer-and-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md index 3bd5a25af0..ae682ab7e9 100644 --- a/beta/src/pages/learn/scaling-up-with-reducer-and-context.md +++ b/beta/src/pages/learn/scaling-up-with-reducer-and-context.md @@ -207,7 +207,7 @@ ul, li { margin: 0; padding: 0; } -Reducer 有助于保持事件处理程序的简短明了。但随着应用规模越来越庞大，你就可能会遇到别的困难。 **目前，`tasks` 状态和 `dispatch` 函数仅在顶级 `TaskBoard` 组件中可用。** 若要让其他组件读取 `tasks` 状态或对其进行更改，必须以 props 的形式显式 [传递](/learn/passing-props-to-a-component) 它。 +Reducer 有助于保持事件处理程序的简短明了。但随着应用规模越来越庞大，你就可能会遇到别的困难。**目前，`tasks` 状态和 `dispatch` 函数仅在顶级 `TaskBoard` 组件中可用。** 若要让其他组件读取 `tasks` 状态或对其进行更改，必须以 props 的形式显式 [传递](/learn/passing-props-to-a-component) 它。 例如，`TaskBoard` 将 `tasks` 和事件处理程序传递给 `TaskList`：