cargdev/angular
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

style: change to American English (#27266)

Browse Source 
PR Close #27266
This commit is contained in:
onlyflix
2018-11-26 09:53:00 +01:00
committed by Jason Aden
parent dabcb3e17b
commit 41e68f7a7a
5 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/animations/browser/src/dsl/animation_ast_builder.ts
View File

@ -26,7 +26,7 @@ const SELF_TOKEN_REGEX = new RegExp(`\s*${SELF_TOKEN}\s*,?`, 'g');
*
* 1. Overlap of animations
* Given that a CSS property cannot be animated in more than one place at the same time, it's
* important that this behaviour is detected and validated. The way in which this occurs is that
* important that this behavior is detected and validated. The way in which this occurs is that
* each time a style property is examined, a string-map containing the property will be updated with
* the start and end times for when the property is used within an animation step.
*

2
packages/compiler-cli/src/ngcc/README.md
View File

@ -23,7 +23,7 @@ yarn bazel test //packages/compiler-cli/src/ngcc/test
## Integration Testing
There are tests that check the behaviour of the overall executable:
There are tests that check the behavior of the overall executable:
```bash
yarn bazel test //packages/compiler-cli/test/ngcc

2
packages/core/test/render3/content_spec.ts
View File

@ -1114,7 +1114,7 @@ describe('content projection', () => {
* being re-assigned from one parent to another. Proposal: have compiler
* to remove all but the latest occurrence of <ng-content> so we generate
* only one P(n, m, 0) instruction. It would make it consistent with the
* current Angular behaviour:
* current Angular behavior:
* http://plnkr.co/edit/OAYkNawTDPkYBFTqovTP?p=preview
*/
it('should project nodes into the last available ng-content', () => {

8
packages/core/test/render3/query_spec.ts
View File

@ -562,13 +562,13 @@ describe('query', () => {
});
/**
* BREAKING CHANGE: this tests asserts different behaviour as compared to Renderer2 when it
* BREAKING CHANGE: this tests asserts different behavior as compared to Renderer2 when it
* comes to descendants: false option and <ng-container>.
*
* Previous behaviour: queries with descendants: false would descend into <ng-container>.
* New behaviour: queries with descendants: false would NOT descend into <ng-container>.
* Previous behavior: queries with descendants: false would descend into <ng-container>.
* New behavior: queries with descendants: false would NOT descend into <ng-container>.
*
* Reasoning: the Renderer2 behaviour is inconsistent and hard to explain to users when it
* Reasoning: the Renderer2 behavior is inconsistent and hard to explain to users when it
* comes to descendants: false interpretation (see
* https://github.com/angular/angular/issues/14769#issuecomment-356609267) so we are changing
* it in ngIvy.