| e4475e6 | dario-piotrowicz | 06 November 2021, 16:57:20 UTC | refactor(core): move outdated comment to view.ts (#44099) remove the comment suggesting to use a const enum for ViewEncapsulation in the renderer3/definitions.ts file and add a similar comment in the view.ts file in which the enum is defined Note: the new comment does not contain the suggestion of changing `None` to `0` as it is unclear what benefits that would bring (for more info see: https://github.com/angular/angular/pull/44099#discussion_r744157686) PR Close #44099 | 10 November 2021, 20:42:20 UTC |
| 5ae679d | ileil | 01 November 2021, 17:50:01 UTC | docs: update review tag to topic (#44008) PR Close #44008 | 10 November 2021, 19:29:13 UTC |
| ee2031d | Pete Bacon Darwin | 03 November 2021, 19:42:02 UTC | fix(compiler): ensure that partially compiled queries can handle forward references (#44113) When a partially compiled component or directive is "linked" in JIT mode, the body of its declaration is evaluated by the JavaScript runtime. If a class is referenced in a query (e.g. `ViewQuery` or `ContentQuery`) but its definition is later in the file, then the reference must be wrapped in a `forwardRef()` call. Previously, query predicates were not wrapped correctly in partial declarations causing the code to crash at runtime. In AOT mode, this code is never evaluated but instead transformed as part of the build, so this bug did not become apparent until Angular Material started running JIT mode tests on its distributable output. This change fixes this problem by noting when queries are wrapped in `forwardRef()` calls and ensuring that this gets passed through to partial compilation declarations and then suitably stripped during linking. See https://github.com/angular/components/pull/23882 and https://github.com/angular/components/issues/23907 PR Close #44113 | 10 November 2021, 18:25:17 UTC |
| f63771e | Pete Bacon Darwin | 08 November 2021, 21:22:32 UTC | refactor(compiler): rename R3ProviderExpression and associated helpers (#44113) This interface will be used in other situations so this change renames it to be more general as `MaybeForwardRefExpression`. PR Close #44113 | 10 November 2021, 18:25:17 UTC |
| bfb2882 | Pei Wang | 21 October 2021, 22:22:39 UTC | ci: Windows support for tsec_test. (#44130) Contents of generated tsconfig for tsec_test now depend on whether Bazel uses symlinked runfiles for nodejs_test. The current implementation assumes that symlinked runfiles are not available on Windows. PR Close #44130 | 10 November 2021, 17:48:48 UTC |
| 18cc5f5 | Pete Bacon Darwin | 09 November 2021, 10:01:56 UTC | test(compiler): remove IE11 match in JIT compiler tests (#44122) Since we no longer support (nor test on) IE11 we can remove these matches for `anonymous` functions. PR Close #44122 | 10 November 2021, 17:37:24 UTC |
| 2256734 | Pavan Kumar Jadda | 10 November 2021, 04:49:46 UTC | docs: updates typescript configuration file links (#44131) The links for `tsconfig.json` target and module sections no longer valid. This commit updates the document with correct links PR Close #44131 | 10 November 2021, 17:37:03 UTC |
| 30a27ad | raman | 04 November 2021, 08:42:55 UTC | fix(platform-browser): use correct parent in animation removeChild callback (#44033) Animation's `onRemovalComplete` callback is using incorrect `parentNode`. Should be parentNode provided by `delegate.parentNode(element)` instead of direct `element.parentNode`. This is not a problem with default renderer but can cause problems with custom renderer if it uses another logic to add/remove nodes. Fixes #44023 PR Close #44033 | 10 November 2021, 01:21:56 UTC |
| 0fdecc4 | Andrew Scott | 04 November 2021, 17:44:21 UTC | refactor(language-service): Move language service code out of ivy/ folder (#44064) This commit moves code in the language service package out of the ivy subfolder. Ivy is the _only_ engine supported in v13+ so there's no need to have a name for it. PR Close #44064 | 10 November 2021, 01:20:05 UTC |
| 789c1d4 | Andrew Scott | 04 November 2021, 17:28:32 UTC | refactor(language-service): Remove View Engine code from language service package (#44064) This commit removes ViewEngine-specific code from the langauge service package. This code is no longer used since VE is not supported in v13+. PR Close #44064 | 10 November 2021, 01:20:05 UTC |
| 04df3a0 | Kristiyan Kostadinov | 08 November 2021, 12:45:34 UTC | fix(compiler-cli): handle pre-release versions when checking version (#44109) Currently the TS version checking function interprets a version like `1.2.3-rc.5` as `1.2.NaN` which would allow it to bypass the version checking altogether. These changes add a little bit more logic to ensure that such versions are handled correctly. There's also an error if we don't manage to parse the version string. Also it seemed like we never actually ran the version check unit tests, because they didn't have a test target. PR Close #44109 | 09 November 2021, 20:54:45 UTC |
| c3d925f | kreuzerk | 06 November 2021, 18:05:53 UTC | docs: including additional assets into libraries (#44076) PR Close #44076 | 09 November 2021, 20:54:22 UTC |
| 192ee90 | Pete Bacon Darwin | 30 October 2021, 20:33:08 UTC | refactor(ngcc): improve logging of progress (#43996) This commit adds additional information to encourage developers to contact the author of View Engine libraries and ask them to update to partial Ivy. Fixes #42308 PR Close #43996 | 09 November 2021, 18:10:19 UTC |
| 47a5136 | George Kalpakas | 08 November 2021, 13:54:17 UTC | build(docs-infra): remove unnecessary work-around for SW config generation (#44114) Since angular.io is now updated to a version that includes the fix from #43679, the work-around added in 841c5aebbfc7f40fdf838cc3e73395cf8b94bdf9 can now be removed. PR Close #44114 | 09 November 2021, 18:08:20 UTC |
| c2f4e97 | Paul Gschwendtner | 04 November 2021, 19:05:29 UTC | ci: instruct renovate to apply patch label to avoid divergence with other version branches (#44065) Renovate currently always applies the minor label. This often causes the patch/FF/RC branches to quickly diverge. We should always apply the patch label with the goal of keeping infra-related changes in sync as much as possible.. Then it is still possible to selectively apply the minor/major label if needed (this forces the reviewer to actually think about where this should go in, if it fails!). PR Close #44065 | 09 November 2021, 18:08:00 UTC |
| c6d023b | dario-piotrowicz | 31 October 2021, 11:18:54 UTC | fix(docs-infra): prevent automatic linking of 'number' (#44000) add 'number' to the ignoreGenericWords set so that it doesn't get wrongly linked to the decimalPipe during the aio docs generation as it is a generic typescript term PR Close #44000 | 09 November 2021, 18:03:39 UTC |
| 1434fad | dario-piotrowicz | 13 October 2021, 21:13:44 UTC | refactor(docs-infra): remove eslint directive comments from examples (#43831) Linting has recently been removed from the examples provided in angular.io (see PRs #43592 and #43746) such removal effects the downloadable and stackblitz examples but linting is still generally used in the examples in the aio project itself (they are being migrated from tslint to eslint in PR #43218) thus eslint directive comments are still necessary in the code itself. So the comments need to be present but need not to be exposed to the users (not in the zips, stackblitzes nor docs themselves), these changes are removing such comments during the examples' parsing phase (effectively removing them from all three sources mentioned above). Original discussion: https://github.com/angular/angular/pull/43218#discussion_r697305494 resolves #43788 PR Close #43831 | 09 November 2021, 18:02:33 UTC |
| 4c700b6 | JoostK | 25 September 2021, 10:50:41 UTC | fix(core): do not use Function constructors in development mode to avoid CSP violations (#43587) This commit removes the dynamic creation of named arrays for internal runtime storage arrays as they may cause CSP violations in development mode, when an application's CSP configuration does not include `unsafe-eval`. Named arrays for view data can still be enabled in development mode using the `ngDevMode=namedConstructors` query parameter when loading the application. The usage of native class syntax for named arrays does not have the desired effect when the code is downleveled to ES5. Since ES5 targets are becoming increasingly more rare this is considered less of a problem than the CSP violation. Fixes #43494 PR Close #43587 | 09 November 2021, 18:02:13 UTC |
| b7d27aa | profanis | 12 December 2020, 18:15:00 UTC | docs(animations): express the seconds in numbers (#40098) I've noticed that the seconds are expressed both by using numbers and words. For example, the doc says `0.5 second` and not `half second`. I believe is more readable to express them by using numbers and is consistent too. PR Close #40098 | 09 November 2021, 18:01:47 UTC |
| dede29e | JoostK | 30 July 2020, 21:08:27 UTC | fix(compiler-cli): ensure literal types are retained when `strictNullInputTypes` is disabled (#38305) Consider the `NgModel` directive which has the `ngModelOptions` input: ```ts class NgModel { @Input() ngModelOptions: { updateOn: 'blur'|'change'|'submit' }; } ``` In a template this may be set using an object literal as follows: ```html <input ngModel [ngModelOptions]="{updateOn: 'blur'}"> ``` This assignment should be accepted, as the object's type aligns with the `ngModelOptions` input in `NgModel`. However, if the `strictNullInputTypes` option is disabled this assignment would inadvertently produce an error: ``` Type '{ updateOn: string; }' is not assignable to type '{ updateOn: "blur"|"change"|"submit"; }'. Types of property 'updateOn' are incompatible. Type 'string' is not assignable to type '"blur"|"change"|"submit"' ``` This is due to the `'blur'` value being inferred to be of type `string` instead of retaining its literal type. The non-null assertion operator that is automatically inserted for input binding assignments when `strictNullInputTypes` is disabled inhibits TypeScript from inferring the string value as its literal type. This commit fixes the issue by omitting the insertion of the non-null operator for object literals and array literals. PR Close #38305 | 09 November 2021, 18:01:25 UTC |
| b8a7124 | Joey Perrott | 08 November 2021, 20:23:45 UTC | refactor(compiler-cli): use relative imports within the @angular/compiler-cli package (#44118) Intrapackage imports should always be done via relative imports rather than using the external import location. PR Close #44118 | 08 November 2021, 22:08:27 UTC |
| 5eac434 | Joey Perrott | 05 November 2021, 21:53:54 UTC | refactor(compiler): reverse testing of ternary operator to ensure typescript properly narrows types (#44089) By checking if the providedIn is a function instead of everything but a function, typescript properly narrows the typings for creating the expressions. PR Close #44089 | 08 November 2021, 21:30:34 UTC |
| 644e1e2 | Pete Bacon Darwin | 06 November 2021, 11:11:06 UTC | docs: update getting started tutorial to use StackBlitz web-containers (#44085) Previous commits changed the docs to use web-container versions for StackBlitz examples. This commit updates the content of the tutorial to match. Fixes #44079 PR Close #44085 | 08 November 2021, 18:12:17 UTC |
| 65fd656 | Pete Bacon Darwin | 05 November 2021, 17:32:55 UTC | build(docs-infra): remove link to custom Stackblitz for running tests (#44085) Previously there was a custom version of the testing app for Stackblitz that would run the tests in the browser. With the web-container approach, this is no longer necessary since the tests can be run directly from the command line. Fixes #44047 PR Close #44085 | 08 November 2021, 18:12:17 UTC |
| 0f64a35 | Pete Bacon Darwin | 05 November 2021, 17:28:21 UTC | build(docs-infra): ensure necessary boilerplate files appear in Stackblitz examples (#44085) The `tsconfig.app.json` and similar were not appearing in the generated Stackblitz examples. PR Close #44085 | 08 November 2021, 18:12:17 UTC |
| 091db9c | Pete Bacon Darwin | 05 November 2021, 17:26:58 UTC | build(docs-infra): remove unused code (#44085) This import was not being used and so it is redundant and can be removed. PR Close #44085 | 08 November 2021, 18:12:17 UTC |
| e5a960b | JoostK | 05 November 2021, 20:18:44 UTC | fix(compiler): generate correct code for safe method calls (#44088) When a safe method call such as `person?.getName()` is used, the compiler would generate invalid code if the argument list also contained a safe method call. For example, the following code: ``` person?.getName(config?.get('title').enabled) ``` would generate ``` let tmp; ctx.person == null ? null : ctx.person.getName((tmp = tmp) == null ? null : tmp.enabled) ``` Notice how the call to `config.get('title')` has completely disappeared, with `(tmp = tmp)` having taken its place. The issue occurred due to how the argument list would be converted from expression AST to output AST twice. First, the outer safe method call would first convert its arguments list. This resulted in a temporary being allocated for `config.get('title')`, which was stored in the internal `_resultMap`. Only after the argument list has been converted would the outer safe method call realize that it should be guarded by a safe access of `person`, entering the `convertSafeAccess` procedure to convert itself. This would convert the argument list once again, but this time the `_resultMap` would already contain the temporary `tmp` for `config?.get('title')`. Consequently, the safe method in the argument list would be emitted as `tmp`. This commit fixes the issue by ensuring that nodes are only converted once. Closes #44069 PR Close #44088 | 08 November 2021, 17:31:37 UTC |
| 0c6c4d8 | Pete Bacon Darwin | 06 November 2021, 13:20:54 UTC | docs: add Angular 13 support information (#44098) Closes #44097 PR Close #44098 | 08 November 2021, 17:03:59 UTC |
| db37f02 | Michael Urban | 02 November 2021, 11:40:53 UTC | docs(animations): update developers on state of package (#44014) Notify developers that @angular/animations package has been "significantly de-prioritized" `animateChild` documentation now references #30477 References #30477# Please enter the commit message for your changes. Lines starting PR Close #44014 | 08 November 2021, 17:03:29 UTC |
| 7e0c7ce | George Kalpakas | 05 November 2021, 17:49:51 UTC | build(docs-infra): fix SystemJS-based docs examples (#43868) Previously, the SystemJS-based docs examples (typically `ngUpgrade` examples) were not compatible with Angular v13 (due to the removal of UMD bundles from the published packages). This commit makes the examples compatible with Angular v13 and re-enables the tests for all SystemJS-based examples on CI. PR Close #43868 | 08 November 2021, 17:01:16 UTC |
| 23d56d7 | George Kalpakas | 05 November 2021, 17:49:51 UTC | build(docs-infra): include `systemjs` as a dependency to SystemJS-based docs examples (#43868) Due to an oversight, the `systemjs` package was previously not included as a dependency in the boilerplate `package.json` file for SystemJS-based docs examples, despite it being required by the app. PR Close #43868 | 08 November 2021, 17:01:16 UTC |
| f367efb | George Kalpakas | 05 November 2021, 17:49:50 UTC | docs(upgrade): minor fixes to the `upgrade` guide (#43868) Includes the following fixes: - Remove unused `format` attribute from `<code-example>` elements - Explicitly mention that the starting point for the "Phonecat Upgrade Tutorial" is the 1.5.x version of the original Phonecat tutorial (since the original tutorial has since been updated to use AngularJS v1.8.x and use npm instead of bower). PR Close #43868 | 08 November 2021, 17:01:16 UTC |
| 3c0daa9 | Renovate Bot | 20 October 2021, 10:22:10 UTC | build: update dependency vlq to v2 (#43901) PR Close #43901 | 08 November 2021, 17:00:56 UTC |
| 8566b78 | Joe Martin (Crowdstaffing) | 02 November 2021, 15:01:35 UTC | docs: update link (#44017) Update link to match heading. PR Close #44017 | 08 November 2021, 17:00:18 UTC |
| f3d9e11 | George Kalpakas | 02 November 2021, 16:37:59 UTC | build(docs-infra): update Angular CLI/framework/Material to final v13 RCs in docs examples (#44030) This commit updates the docs examples to the latest prerelease versions of Angular CLI, framework and CDK/Material. It also updates the apps to more closely align with new apps CLI apps. See also the [diff][1] between a basic v13.0.0-rc.0 CLI app and a v13.0.0-rc.2 one. [1]: cexbrayat/angular-cli-diff@13.0.0-rc.0...13.0.0-rc.2 PR Close #44030 | 08 November 2021, 16:59:47 UTC |
| 06b2023 | Paul Gschwendtner | 29 October 2021, 15:55:17 UTC | test: update size goldens for AIO after updating to final v13 RCs (#44030) Updates the size goldens for AIO to reflect the new measurements after the v13 update to the latest release-candidates. i.e. * rc.3 of Angular framework * rc.2 of Angular CDK/Material * rc.3 of Angular CLI. Co-authored-by: George Kalpakas <kalpakas.g@gmail.com> PR Close #44030 | 08 November 2021, 16:59:47 UTC |
| f477d0c | Paul Gschwendtner | 29 October 2021, 15:14:59 UTC | build(docs-infra): update AIO to angular framework/components/cli final RCs (#44030) Updates AIO to the latest v13 release-candidate version of all Angular-owned packages, such as Angular CDK and Angular Material. Applies changes needed for the v13 CLI as performed by the CLI through `ng update`: https://github.com/angular/angular-cli/tree/7ff8c5350ea2e49574dd659adae02215957d2685/packages/schematics/angular/migrations/update-13. Additionally, the web components polyfill has been removed as all browsers supported by Angular seem to support custom elements v1 natively, according to: * https://caniuse.com/custom-elementsv1 * https://www.webcomponents.org/ (scroll down to browser support) Co-authored-by: George Kalpakas <kalpakas.g@gmail.com> PR Close #44030 | 08 November 2021, 16:59:47 UTC |
| 12769e3 | Renovate Bot | 25 October 2021, 17:11:39 UTC | build: update angular (#44030) Update all `@angular/*` and `@schematics/*` root dependencies to latest versions. PR Close #44030 | 08 November 2021, 16:59:47 UTC |
| 6a36483 | Roman Frołow | 05 November 2021, 10:05:52 UTC | docs(forms): fix typo in toInteger() function (#44075) PR Close #44075 | 08 November 2021, 16:59:08 UTC |
| 5b1938c | Joey Perrott | 05 November 2021, 19:59:28 UTC | refactor(core): correct typing when getting the Nearest LContainer (#44087) Updating the casted typings of `getNearestLContainer` to ensure that typescript properly returns the LContainer | null type. PR Close #44087 | 05 November 2021, 21:31:50 UTC |
| bc6f0a0 | Joey Perrott | 05 November 2021, 19:22:49 UTC | refactor(core): correct typing checks when registering destroy hooks (#44087) Making the typing filtering more explicit allows typescript to properly recognize the presence of the `prototype` property on the provider within the `registerDestroyHooksIfSupported` method. PR Close #44087 | 05 November 2021, 21:31:50 UTC |
| c96ba23 | Joey Perrott | 05 November 2021, 19:13:30 UTC | refactor(core): remove truthy check for classes getter (#44087) Remove the truthy check for the classes getter as both paths from the check assume className was not undefined. This allows for typescript to properly determine the type of `className` in the falsy path from the truthy check. PR Close #44087 | 05 November 2021, 21:31:50 UTC |
| 210f7e5 | iRealNirmal | 14 October 2021, 04:06:32 UTC | refactor(forms): update minlength/maxlength to inherit abstractValidator (#43998) Modified minlength and maxlength validator to inherit abstractValidator For every validator type different PR will be raised as discussed in #42378. Closes #42267 PR Close #43998 | 05 November 2021, 20:09:53 UTC |
| 8f840c3 | Joey Perrott | 18 October 2021, 16:31:22 UTC | ci: update mobile browsers tested via browser stack to correctly test supported browsers (#44083) Update to running tests against latest ios and android emulators. PR Close #44083 | 05 November 2021, 19:55:42 UTC |
| e0420d3 | Joey Perrott | 15 October 2021, 18:59:46 UTC | docs: remove reference of testing against BrowserStack (#44083) Remove BrowserStack from statement about CI tests using the service as Angular now only uses Saucelabs for our platform specific browser testing. PR Close #44083 | 05 November 2021, 19:55:42 UTC |
| 4562a03 | Joey Perrott | 15 October 2021, 18:58:42 UTC | docs: update listed supported browsers to accurately reflect support browsers (#44083) Update documentation to note 2 most recent major versions of Android browser support rather than explictly listing browsers. PR Close #44083 | 05 November 2021, 19:55:42 UTC |
| 58f453d | A. Singh | 03 November 2021, 16:52:26 UTC | docs: improve documentation (#44031) PR Close #44031 | 05 November 2021, 16:23:50 UTC |
| e0c25f8 | Paul Gschwendtner | 04 November 2021, 10:26:00 UTC | build: add angular v12 packages to renovate ignore list (#44054) The Angular v12 alias packages should not be accidentally updated to v13 by Renovate. These packages are still used by tests for e.g. Ngcc and should continue to provide the APF v12 View Engine output. PR Close #44054 | 05 November 2021, 16:22:54 UTC |
| 4ccb768 | Paul Gschwendtner | 04 November 2021, 17:10:13 UTC | ci: do not capture nested bazel integration test workspace within Bazel (#44061) The `integration/bazel` folder cannot be excluded within the `.bazelignore` file. This is necessary so that the integration test rule can glob for all files within the integration test. The downside is that the `integration/bazel/<..>` folder is being discovered by the `//...` target query, causing Starlark files to be interpreted/validated. e.g. https://app.circleci.com/pipelines/github/angular/angular/39255/workflows/c6c448ed-9a44-49b3-a0c2-2c7328ce2855/jobs/1079169 Previously such errors did not appear because no Starlark `.bzl` files within the test imported other files using the `//` absolute resolution. Explicitly excluding the nested packages using the `--deleted_packages` option is the most idiomatic way of achieving this currently (similarly done by `rules_nodejs`). More information on why this is so verbose currently: https://github.com/bazelbuild/bazel/issues/12034 PR Close #44061 | 05 November 2021, 16:22:18 UTC |
| fba7bc0 | Paul Gschwendtner | 04 November 2021, 15:42:03 UTC | refactor(bazel): fix typo in packager action file comments (#44061) Fixes two typoes in the packager logic. PR Close #44061 | 05 November 2021, 16:22:18 UTC |
| bfc8bdb | Paul Gschwendtner | 04 November 2021, 15:40:58 UTC | test: re-enable bazel integration test with APF v13 (#44061) Re-enables the Bazel integration test that we have disabled as part of the APF v13 changes. Since there are no UMD files anymore, the Karma tests no longer worked. Similarly, the Angular linker had to run for building the production bundle. PR Close #44061 | 05 November 2021, 16:22:18 UTC |
| 33e5171 | Aristeidis Bampakos | 05 November 2021, 11:53:52 UTC | docs: update install guide for angular elements (#44077) Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com> PR Close #44077 | 05 November 2021, 16:21:58 UTC |
| 68cc2e2 | Alan Agius | 04 November 2021, 14:24:57 UTC | docs: update Definition of Terms in APF guide (#44060) Several improvements to the Definition of Terms of terms section in the APF guide. PR Close #44060 | 04 November 2021, 18:59:14 UTC |
| 86980aa | Alan Agius | 04 November 2021, 14:10:36 UTC | docs: unlink `async` keyword in APF guide (#44060) Currently, `async` keywords in the APF guide incorrectly links to https://angular.io/api/common/AsyncPipe PR Close #44060 | 04 November 2021, 18:59:14 UTC |
| 980b173 | Alan Agius | 04 November 2021, 14:07:47 UTC | docs: update apf guide files layouts table (#44060) With this change we improve the file layout structure table and align it with other similar tables example: https://angular.io/guide/file-structure PR Close #44060 | 04 November 2021, 18:59:14 UTC |
| 00420fa | Paul Gschwendtner | 04 November 2021, 10:56:42 UTC | test: re-enable platform-server integration test (#44055) Re-enables the platform-server integration test that we had to disable when we landed the APF v13 changes. We can re-enable it by setting up the `fullySpecified` option similar to how the CLI does it. PR Close #44055 | 04 November 2021, 18:57:22 UTC |
| 5377cad | mgechev | 03 November 2021, 18:55:06 UTC | docs: update roadmap update date (#44036) PR Close #44036 | 04 November 2021, 18:56:14 UTC |
| cbe3086 | Alan Agius | 03 November 2021, 16:38:01 UTC | build(docs-infra): configure region parser to allow `.mjs` (#44027) This commit updates the necessary config settings to allow `.mjs` files to be able to be parsed by the region parser. We configure the parser to use `inline-c-only` so that comments are generated in like the below ``` // #docregion ``` rather than ``` /* #docregion */ ``` PR Close #44027 | 04 November 2021, 18:55:52 UTC |
| 007a616 | Alan Agius | 03 November 2021, 08:10:50 UTC | docs: improve consuming partial-Ivy code outside the Angular CLI (#44027) With this change we add an example of how to consume the linker plugin and also clean up the parts of this section. Closes #44026 PR Close #44027 | 04 November 2021, 18:55:52 UTC |
| 42034bc | mgechev | 02 November 2021, 16:49:49 UTC | docs: update the survey expiry date (#44021) PR Close #44021 | 04 November 2021, 18:55:24 UTC |
| 739cb1d | Paul Gschwendtner | 02 November 2021, 14:43:57 UTC | test: update ng-update integration test to test v13 migrations (#44016) Updates the `ng-update` migration integration test to run against v13 migrations. We have removed all older migrations so this integration test needs to be updated. PR Close #44016 | 04 November 2021, 18:54:55 UTC |
| dfa92f3 | Paul Gschwendtner | 02 November 2021, 14:14:04 UTC | test: re-enable ng-update migration integration test (#44016) Re-enables the ng-update migration integration test as all the ESM/CJS interop changes have landed in the `@angular/core` schematics folder. PR Close #44016 | 04 November 2021, 18:54:55 UTC |
| 7d12e7b | Paul Gschwendtner | 02 November 2021, 14:13:00 UTC | test: wire up `ng-add-localize` CLI project as integration test to run within Bazel (#44016) Wires up the `ng-add-localize` minimal CLI project to run as integration test within Bazel. PR Close #44016 | 04 November 2021, 18:54:55 UTC |
| 6797431 | Paul Gschwendtner | 02 November 2021, 14:06:10 UTC | refactor(localize): ensure schematic code runs as commonjs (#44016) The schematic code in `@angular/localize` is currently still emitted as CommonJS, while the rest of `@angular/localize` is strict ESM (which is also denoted through `type: module` in the package.json file). The schematic code is currently imported as CJS from the CLI so it is not a problem right now. Still, it is safer to ensure the code for schematics is properly picked up as CJS through a local `package.json` file resetting `type: module` to `type: commonjs`. PR Close #44016 | 04 November 2021, 18:54:55 UTC |
| 2c777b9 | Paul Gschwendtner | 02 November 2021, 14:03:53 UTC | test: setup minimal CLI project for ng-add localize integration test (#44016) Sets up a minimal CLI project for testing that `ng add @angular/localize` works as expected. Schematic sub-packages are prone to CJS/ESM issues due the overall framework packages being denoted as strict ESM. This may not be an issue in the concrete scenario of `@angular/localize` right now, but it is still good to have an integration test similar to the tests we have for `@angular/core` schematics. PR Close #44016 | 04 November 2021, 18:54:55 UTC |
| c809e4b | Renovate Bot | 20 October 2021, 08:43:06 UTC | build: update dependency tsec to v0.1.10 (#43899) (#44010) Updates the tsec dependency to v0.1.10 so that the Tsec Windows support PR can land. PR Close #43899 PR Close #44010 | 04 November 2021, 18:54:21 UTC |
| 5be8bd4 | Joel Lefkowitz | 26 October 2021, 11:59:35 UTC | docs: amend inaccurate immutability definition (#43951) (#43951) PR Close #43951 PR Close #43951 | 04 November 2021, 18:53:18 UTC |
| 80310b0 | Joey Perrott | 28 October 2021, 22:47:19 UTC | refactor(core): set up structure for google3 usage of migration schematics (#43980) Set up exporting the migration rules from the google3 directly from the internal @angular/migrations package. This package is an internal only package to be exposed for loading TSLint rules. PR Close #43980 | 04 November 2021, 18:23:12 UTC |
| ef15db0 | Joey Perrott | 04 November 2021, 00:20:03 UTC | docs: add blog post link to CHANGELOG (#44050) PR Close #44050 | 04 November 2021, 00:26:22 UTC |
| 0744075 | Andrew Kushnir | 03 November 2021, 18:19:03 UTC | docs: update CHANGELOG with deprecations (#44035) This commit adds deprecation messages from the commits in the `.next` and `.rc` releases. PR Close #44035 | 04 November 2021, 00:03:34 UTC |
| 9741473 | Joey Perrott | 03 November 2021, 22:56:35 UTC | ci: update aio payloads size (#44046) Update the payloads size for aio tracking. PR Close #44046 | 03 November 2021, 23:37:11 UTC |
| ea77439 | Joey Perrott | 03 November 2021, 22:37:33 UTC | fix(docs-infra): remove tilda from scss imports in aio (#44046) Remove tilda usages. PR Close #44046 | 03 November 2021, 23:37:11 UTC |
| 35e3809 | Alex Rickabaugh | 03 November 2021, 21:27:21 UTC | build(docs-infra): update to 13.0.0 (#44046) This commit updates AIO to use the published 13.0.0 packages, as the final step after the release. PR Close #44046 | 03 November 2021, 23:37:10 UTC |
| 1e11648 | Joey Perrott | 03 November 2021, 22:05:13 UTC | build: update lock files (#44046) Update the lock files and add --frozen-lockfile flag to the aio presetup command. PR Close #44046 | 03 November 2021, 23:37:10 UTC |
| b361242 | Pete Bacon Darwin | 03 November 2021, 21:24:01 UTC | build(docs-infra): target webcontainers for stackblitz "live-example" links (#44041) This commit changes the Stackblitz live examples to create "webcontainer" projects on Stackblitz. This approach supports the new Angular v13 packaging formats but webcontainers are not supported on some browers. So this is a temporary solution. PR Close #44041 | 03 November 2021, 23:19:56 UTC |
| 167e2a8 | Alex Rickabaugh | 03 November 2021, 17:44:19 UTC | release: cut the v13.0.0 release (#44032) PR Close #44032 | 03 November 2021, 17:51:28 UTC |
| b6f2a55 | Paul Gschwendtner | 02 November 2021, 15:17:44 UTC | fix(migrations): prevent migrations from updating external templates multiple times (#44013) The `NgComponentTemplateVisitor` helper was always referring back to the original source file on disk rather than the virtual file in the migration. This meant that some template migrations could attempt to modify the template multiple times resulting in invalid output. As an example the `migration-v13-router-link-empty-expression` migrates the following template: ``` <div [routerLink]></div> ``` to ``` <div [routerLink]="[]"></div> ``` But if the template was referenced multiple times in the program, such as when the component was referenced in the source and test entry-points, the migration would result in things like: ``` <div [routerLink]="[]"="[]"></div> ``` Fixes #44005. PR Close #44013 | 03 November 2021, 16:38:44 UTC |
| 95a68c5 | Pete Bacon Darwin | 02 November 2021, 10:23:59 UTC | fix(migrations): account for CRLF characters in template migrations (#44013) Previously, when parsing code for templates to migrate, CRLF characters were converted to just LF. This meant that the source-spans being used to overwrite the template strings in the original source code were out of sync with the positions identified in the parsed templates. This commit fixes this by parsing the raw text of the template taken from the source code instead of processed string contents. Fixes #44005 PR Close #44013 | 03 November 2021, 16:38:44 UTC |
| 59f12c3 | Pete Bacon Darwin | 02 November 2021, 10:19:55 UTC | ci: re-enable the schematics tests (#44013) These tests had been disabled when we initially disabled ViewEngine. The tests appear to run fine despite this, so we can re-enable them. PR Close #44013 | 03 November 2021, 16:38:44 UTC |
| d24cbce | Alex Rickabaugh | 02 November 2021, 01:38:20 UTC | release: cut the v13.0.0-rc.3 release (#44011) PR Close #44011 | 02 November 2021, 01:50:22 UTC |
| 4fd388b | Alex Rickabaugh | 29 October 2021, 22:30:32 UTC | docs: initial commit of Angular Package Format documentation (#43987) This commit adds the Angular Package Format to AIO. Previously this document was updated and versioned in Google Docs. The document is also updated for the Angular Package Format version 13. PR Close #43987 | 02 November 2021, 01:24:21 UTC |
| 74c4972 | Joe Martin (Crowdstaffing) | 01 November 2021, 22:28:54 UTC | docs: update per feedback (#44009) Update content per feedback from previous PR. PR Close #44009 | 02 November 2021, 00:38:54 UTC |
| 892ded5 | mgechev | 29 October 2021, 20:23:26 UTC | docs: update the roadmap in alignment with v13 progress (#43986) PR Close #43986 | 01 November 2021, 21:02:14 UTC |
| 87bcb3f | Andrew Scott | 01 November 2021, 15:47:07 UTC | Revert "refactor(router): restore history in a consistent way on canceled navigations (#43651)" (#44006) This reverts commit a268c4471f2e1dcaffe3304236d506222adab44c. Causes failures in internal team's code. The failures likely relate to attempting to manually update private Router state tracking properties, which this change would have affected. PR Close #44006 | 01 November 2021, 16:25:36 UTC |
| 0382f86 | Joe Martin (Crowdstaffing) | 29 October 2021, 21:00:30 UTC | docs: update left-nav (#43964) Update left-nav toc. PR Close #43964 | 29 October 2021, 23:51:34 UTC |
| 0a51212 | Joe Martin (Crowdstaffing) | 29 October 2021, 20:42:30 UTC | docs: add link (#43964) Add link for RFC. Clean up markdown formatting. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| dd79d31 | Joe Martin (Crowdstaffing) | 29 October 2021, 20:19:28 UTC | docs: update per tech review (#43964) Update content per feedback in tech review. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| c971889 | Joe Martin (Crowdstaffing) | 27 October 2021, 18:51:09 UTC | docs: update release notes (#43964) Update release note for version 13. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| 618a9c7 | Joe Martin (Crowdstaffing) | 27 October 2021, 18:38:10 UTC | docs: add redirect test (#43964) Add redirect test for new latest version topic. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| 4e57cab | Joe Martin (Crowdstaffing) | 27 October 2021, 18:34:41 UTC | docs: add links (#43964) docs: add links to additional information. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| a23942e | Joe Martin (Crowdstaffing) | 27 October 2021, 18:15:04 UTC | docs: remove previous latest verison (#43964) Remove content for previous latest version. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| b671a37 | Joe Martin (Crowdstaffing) | 27 October 2021, 17:34:06 UTC | docs: update migration content (#43964) Update content for AngularJS to Angular migration. Add note to manually create UMD bundles. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| a4dc5da | Joe Martin (Crowdstaffing) | 27 October 2021, 17:30:32 UTC | docs: update library use content (#43964) Update content for library use. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| 97eed3e | Joe Martin (Crowdstaffing) | 27 October 2021, 17:29:07 UTC | docs: add latest version content (#43964) Add the update to latest version content for version 13. Add redirect for latest version content. Update toc for later version content. PR Close #43964 | 29 October 2021, 23:51:33 UTC |
| 9c99afd | Alan Agius | 29 October 2021, 14:22:46 UTC | fix(docs-infra): search box input line-height (#43983) This fixes an issue on Safari which caused the text to be pushed down when blurring out of the search input field. The root cause of the problem appears to be that previously the computed line height was that of 32px, which caused a shift in content. Closes #43935 PR Close #43983 | 29 October 2021, 22:47:09 UTC |
| 6b24855 | Joe Martin (Crowdstaffing) | 28 October 2021, 22:23:10 UTC | docs: update note (#43979) Update the note for hierarchy of locale identifiers. PR Close #43979 | 29 October 2021, 22:46:37 UTC |
| aea63fc | Joe Martin (Crowdstaffing) | 28 October 2021, 22:17:09 UTC | docs: remove link (#43979) Remove redundant link. PR Close #43979 | 29 October 2021, 22:46:37 UTC |
| f4ea80a | Andrew Kushnir | 28 October 2021, 21:41:19 UTC | refactor(core): add `ViewRef` to private exports (#43978) This commit adds `ViewRef` to private exports, so it can be reused in internal packages. The `ViewRef` symbol remains *private* and should not be referenced directly. PR Close #43978 | 29 October 2021, 22:45:50 UTC |
| 494d056 | George Kalpakas | 28 October 2021, 16:01:44 UTC | refactor(docs-infra): remove obsolete way of disabling `DocViewer` animations (#43977) Previously, there were two ways to disable view transition animations in `DocViewerComponent`: Using a `.no-animations` CSS class on the `<aio-doc-viewer>` element and setting the static `DocViewerComponent.animationsEnabled` property to `false`. The latter was only used to disable animations for testing purposes. With the recent introduction of `AppComponent.reducedMotion`, there is now an easy way to disable animations in tests using the `.no-animations` class (which is applied by `AppComponent` based on the value of `AppComponent.reducedMotion`). Therefore, it is no longer necessary to have `DocViewerComponent.animationEnabled`. This commit removes the now obsolete `animationsEnalbed` property. PR Close #43977 | 29 October 2021, 22:45:02 UTC |
| 22c5f35 | George Kalpakas | 28 October 2021, 16:01:44 UTC | fix(docs-infra): improve accessibility by respecting `prefers-reduced-motion` (#43977) Make the app easier to use for people with motion sensitivities by disabling several animations (esp. ones involving moving things around) when the user prefers reduced motion. The user's preference is detected using the [prefers-reduced-motion][1] CSS media feature. Disabled animations include: - View fade in/out transitions. - Sidenav open/close animations. - Top-menu color and size changes. - Contributor cards flip animations. For more details on using `prefers-reduced-motion` and disabling Angular animations see: - [Designing with reduced motion for motion sensitivities][2] - [Disabling Angular animations at runtime][3] [1]: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion [2]: https://www.smashingmagazine.com/2020/09/design-reduced-motion-sensitivities/ [3]: https://dev.to/this-is-angular/disabling-angular-animations-at-runtime-9a6 PR Close #43977 | 29 October 2021, 22:45:02 UTC |
