fix: 文字微调
This commit is contained in:
parent
9947285236
commit
73312fdafc
@ -22,7 +22,7 @@ Transforming a component to a custom element makes all of the required Angular i
|
||||
Creating a custom element is simple and straightforward, and automatically connects your component-defined view with change detection and data binding, mapping Angular functionality to the corresponding native HTML equivalents.
|
||||
|
||||
把组件转换成自定义元素可以让所有所需的 Angular 基础设施都在浏览器中可用。
|
||||
创建自定义元素的方式简单直接,并且会自动把你组件定义的视图连同变更检测与数据绑定等 Angular 的功能映射为相应的原生 HTML 等价物。
|
||||
创建自定义元素的方式简单直观,它会自动把你组件定义的视图连同变更检测与数据绑定等 Angular 的功能映射为相应的原生 HTML 等价物。
|
||||
|
||||
<div class="alert is-helpful">
|
||||
|
||||
|
@ -516,7 +516,7 @@ If forms are a central part of your application, scalability is very important.
|
||||
|
||||
Choosing a strategy begins with understanding the strengths and weaknesses of the options presented. Low-level API and form model access, predictability, mutability, straightforward validation and testing strategies, and scalability are all important considerations in choosing the infrastructure you use to build your forms in Angular. Template-driven forms are similar to patterns in AngularJS, but they have limitations given the criteria of many modern, large-scale Angular apps. Reactive forms minimize these limitations. Reactive forms integrate with reactive patterns already present in other areas of the Angular architecture, and complement those requirements well.
|
||||
|
||||
要选择一项策略就要先了解所提供选项的优缺点。当决定在 Angular 中构建表单要选择哪种基础设施时,底层 API 访问、表单模型访问、可预测性、可变性、直截了当的验证方式和测试策略以及可伸缩性都是重要的考虑因素。
|
||||
要选择一项策略就要先了解所提供选项的优缺点。当决定在 Angular 中构建表单要选择哪种基础设施时,底层 API 访问、表单模型访问、可预测性、可变性、直观的验证方式和测试策略以及可伸缩性都是重要的考虑因素。
|
||||
模板驱动表单和 AngularJS 中的传统模式相似,但它们具有局限性。响应式表单已经和 Angular 架构的其它部分存在的响应式模式相整合,并很好地弥补了这些需求。
|
||||
|
||||
## Next steps
|
||||
|
@ -24,7 +24,7 @@ Reactive forms use an explicit and immutable approach to managing the state of a
|
||||
|
||||
Reactive forms also provide a straightforward path to testing because you are assured that your data is consistent and predictable when requested. Any consumers of the streams have access to manipulate that data safely.
|
||||
|
||||
响应式表单还提供了一种更直白的测试路径,因为在请求时你可以确信这些数据是一致的、可预料的。这个流的任何一个消费者都可以安全地操纵这些数据。
|
||||
响应式表单还提供了一种更直观的测试路径,因为在请求时你可以确信这些数据是一致的、可预料的。这个流的任何一个消费者都可以安全地操纵这些数据。
|
||||
|
||||
Reactive forms differ from template-driven forms in distinct ways. Reactive forms provide more predictability with synchronous access to the data model, immutability with observable operators, and change tracking through observable streams. If you prefer direct access to modify data in your template, template-driven forms are less explicit because they rely on directives embedded in the template, along with mutable data to track changes asynchronously. See the [Forms Overview](guide/forms-overview) for detailed comparisons between the two paradigms.
|
||||
|
||||
|
@ -3042,7 +3042,7 @@ The unit test files themselves also need to be switched to Angular when their pr
|
||||
counterparts are switched. The specs for the checkmark pipe are probably the most straightforward,
|
||||
as the pipe has no dependencies:
|
||||
|
||||
如果产品代码被切换到了 Angular,单元测试文件本身也需要切换过来。对勾(checkmark)管道的规约可能是最简单的,因为它没有任何依赖:
|
||||
如果产品代码被切换到了 Angular,单元测试文件本身也需要切换过来。对勾(checkmark)管道的规约可能是最直观的,因为它没有任何依赖:
|
||||
|
||||
<code-example path="upgrade-phonecat-2-hybrid/app/core/checkmark/checkmark.pipe.spec.ts" header="app/core/checkmark/checkmark.pipe.spec.ts">
|
||||
</code-example>
|
||||
|
@ -9,7 +9,7 @@ You begin by creating an initial application using the Angular CLI. Throughout t
|
||||
|
||||
In this part of the tutorial, you'll do the following:
|
||||
|
||||
在教程的这个部分,你要做下列工作:
|
||||
在教程的这个部分,你将完成下列工作:
|
||||
|
||||
1. Set up your environment.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user