| 7307ea3 | Alan Agius | 29 October 2021, 09:45:42 UTC | test: remove `ng_elements_schematics` integration test (#43975) This test has been removed as since the elements schematic has been removed in a previous commit. PR Close #43975 | 29 October 2021, 22:43:56 UTC |
| f544a53 | Alan Agius | 29 October 2021, 09:28:30 UTC | fix(elements): remove incorrect `@angular/platform-browser` peer dependency (#43975) The elements package doesn't use `@angular/platform-browser` therefore this is not needed. PR Close #43975 | 29 October 2021, 22:43:56 UTC |
| a468213 | Alan Agius | 28 October 2021, 12:08:59 UTC | fix(elements): remove `ng-add` schematic (#43975) This schematic is no longer needed since all the [browsers](https://angular.io/guide/browser-support) that Angular supports `CustomElementRegistry` APIs. Side note: `document-register-element` has been deprecated in favor of `@ungap/custom-element` PR Close #43975 | 29 October 2021, 22:43:56 UTC |
| 8f7ceae | Alan Agius | 28 October 2021, 11:26:03 UTC | docs: update elements page (#43975) This section was outdated since now all CLI projects are es2015+ and don't require the polyfill since legacy browsers are no longer supported. PR Close #43975 | 29 October 2021, 22:43:56 UTC |
| fce7bb8 | Alan Agius | 28 October 2021, 11:19:05 UTC | test: remove `document-register-element` from elements tests (#43975) All the [browsers](https://angular.io/guide/browser-support) that Angular supports `CustomElementRegistry` APIs PR Close #43975 | 29 October 2021, 22:43:56 UTC |
| c50abe5 | Andrew Kushnir | 20 October 2021, 04:25:51 UTC | docs: update dynamic component guide to use factory-less ViewContainerRef.createComponent (#43895) PR Close #43895 | 29 October 2021, 22:39:04 UTC |
| 3084df8 | George Kalpakas | 29 October 2021, 11:17:16 UTC | ci: improve angular.io deployment process for the master branch (#43963) Previously, the master branch was only deployed to the `next-angular-io-site` Firebase site, which is connected to the `next.angular.io` domain. However, if the master major version was higher than the stable major version (or the RC major version in case there was an active RC), we also had to manually configure (via the Firebase console and/or DNS records) the `v<X>.angular.io` domain to redirect to `next.angular.io`. Then, once `<X>` became the new stable or RC version, we had to manually remove the redirect (to let `v<X>.angular.io` be redirected to `angular.io` or `rc.angular.io`). This commit is part of a new process that reduces the manual steps as follows (the steps below only apply when the master major version is higher than the current stable and RC (if applicable)): - A `v<X>-angular-io-site` Firebase site will be created as soon as the version in the `master` branch's `package.json` is updated to a new major. - The `v<X>.angular.io` domain will be connected to that new Firebase site. - When deploying from the master branch, we will deploy to both `next-angular-io-site` and `v<X>-angular-io-site`. In addition, the deployment to `v<X>-angular-io-site` will update the Firebase config file to redirect to `next.angular.io`. - When the master version becomes the new stable/RC, we will start deploying to `v<X>-angular-io-site` from the stable/RC branch, which will update the Firebase config to stop redirecting to `next.angular.io` and redirect to `(rc.)angular.io` instead (without requiring changes in the Firebase console or DNS). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| 6662fcf | George Kalpakas | 29 October 2021, 11:17:15 UTC | ci: improve angular.io deployment process for the RC branch (#43963) Previously, (when there was an active RC) the RC branch was only deployed to the `rc-angular-io-site` Firebase site, which is connected to the `rc.angular.io` domain. However, if the RC major version was higher than the stable major version, we also had to manually configure (via the Firebase console and/or DNS records) the `v<X>.angular.io` domain to redirect to `rc.angular.io`. Then, once `<X>` became the new stable version, we had to manually remove the redirect (to let `v<X>.angular.io` be redirected to `angular.io`). This commit is part of a new process that reduces the manual steps as follows (the steps below only apply to RC versions that have a higher major version than the current stable): - A `v<X>-angular-io-site` Firebase site will be created for the new RC version. - The `v<X>.angular.io` domain will be connected to that new Firebase site. - When deploying from the RC branch, we will deploy to both `rc-angular-io-site` and `v<X>-angular-io-site`. In addition, the deployment to `v<X>-angular-io-site` will update the Firebase config file to redirect to `rc.angular.io`. - When the RC version becomes the new stable, we will start deploying to `v<X>-angular-io-site` from the stable branch, which will update the Firebase config to stop redirecting to `rc.angular.io` and redirect to `angular.io` instead (without requiring changes in the Firebase console or DNS). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| 40abf03 | George Kalpakas | 29 October 2021, 11:17:15 UTC | ci: improve angular.io deployment process for the stable branch (#43963) Previously, the stable branch was always deployed to the `v<X>-angular-io-site` Firebase site, which was connected to the `angular.io` domain. Whenever a new major version was released (and became the new stable version), the `angular.io` domain had to be disconnected from the previous Firebase site and be connected to the new `v<Y>-angular-io-site` Firebase site. This was a manual process that involved making changes in the Firebase console and the DNS records. This commit is part of a new process that reduces the manual steps as follows: - A new `stable-angular-io-site` Firebase site is created. - The `angular.io` domain will be connected to that new Firebase site. - When deploying from the stable branch, we will deploy to both `stable-angular-io-site` and `v<X>-angular-io-site`. In addition, the deployment to `v<X>-angular-io-site` will update the Firebase config file to redirect to `angular.io`. - When a new major version is released, we will start deploying from the new stable branch to `stable-angular-io-site`, but there will be no need to connect/disconnect the `angular.io` domain. Also, `v<X>.angular.io` will stop redirecting to `angular.io` by means of updating the Firebase config file (without requiring changes in the Firebase console or DNS). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| d1321a1 | George Kalpakas | 29 October 2021, 11:17:15 UTC | feat(docs-infra): add post-deploy actions for testing more redirect configs (#43963) Add `deploy-to-firebase` post-deploy actions to allow testing various redirect configs. In a future commit, this will allow testing redirects for the `stable`, `rc` and `next` deployments via the Firebase config file (without requiring changes in the Firebase console or DNS). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| f5d236b | George Kalpakas | 29 October 2021, 11:17:15 UTC | refactor(docs-infra): make it easier to configure Firebase redirects at deployment (#43963) Refactor the `deploy-to-firebase` post-deploy actions by extracting logic to separate helper functions. This makes it easier to create more functions for testing various redirect configs (in a future commit). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| 78d0bda | George Kalpakas | 29 October 2021, 11:17:15 UTC | feat(docs-infra): add more granular support for configuring Firebase redirects at deployment (#43963) Previously, there was a `deploy-to-firebase` pre-deploy action for configuring Firebase to redirect non-file requests to `angular.io`. This is used for ensuring that `rc.angular.io` is correctly redirected to `angular.io`, even when people have previously visited (and have a ServiceWorker activated on) `rc.angular.io`. This commit adds pre-deploy actions for configuring Firebase to redirect a deployment to any of `angular.io`, `rc.angular.io` or `next.angular.io` and also configure whether all requests or only non-file requests will be redirected. In a future commit, this will allow managing redirects for the `stable`, `rc` and `next` deployments via the Firebase config file (without requiring changes in the Firebase console or DNS). PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| 609579c | George Kalpakas | 29 October 2021, 11:17:14 UTC | feat(docs-infra): create undo functions for all pre-deploy actions (#43963) Create functions to undo the changes made by any pre-deploy action. In a future commit, this will allow deploying a build to multiple projects/sites with different small tweaks for each. PR Close #43963 | 29 October 2021, 22:05:11 UTC |
| 57e6339 | George Kalpakas | 29 October 2021, 11:17:14 UTC | test(docs-infra): avoid running expensive operations when focusing/skipping tests (#43963) Previously, the pre-computation of branch version info for the `deploy-to-firebase` tests would always take place even when the tests that used that info were skipped. This pre-computation involves network access and may add a noticeable delay. This commit refactors the tests to not do the pre-computation if the corresponding tests are skipped. This allows for a faster iteration when focusing on a different set of tests. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 4c22339 | George Kalpakas | 29 October 2021, 11:17:14 UTC | refactor(docs-infra): move `deploy-to-firebase` post-deploy actions to a separate file (#43963) Move some functions that are used as post-deploy actions from `deploy-to-firebase/index.mjs` to a separate file (`deploy-to-firebase/post-deploy-actions.mjs`) to keep `index.mjs` small and easier to maintain. NOTE: While not strictly necessary atm, `post-deploy-actions.mjs` uses the same default export pattern for consistency with `utils.mjs`. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 5049124 | George Kalpakas | 29 October 2021, 11:17:13 UTC | refactor(docs-infra): move `deploy-to-firebase` pre-deploy actions to a separate file (#43963) Move some functions that are used as pre-deploy actions from `deploy-to-firebase/index.mjs` to a separate file (`deploy-to-firebase/pre-deploy-actions.mjs`) to keep `index.mjs` small and easier to maintain. Also, rename the `removeServiceWorker()` function to `disableServiceWorker()`, which is a little more accurate. NOTE: While not strictly necessary atm, `pre-deploy-actions.mjs` uses the same default export pattern for consistency with `utils.mjs`. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 6d7c2e0 | George Kalpakas | 29 October 2021, 11:17:13 UTC | refactor(docs-infra): move `deploy-to-firebase` util functions to a separate file (#43963) Move some util functions from `deploy-to-firebase/index.mjs` to a separate file (`deploy-to-firebase/utils.mjs`) to keep `index.mjs` small and easier to maintain. NOTE: To make it easier to mock functions in tests, `utils.mjs` uses a default export (instead of multiple named exports) and references local functions through the default exported object. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 7120a00 | George Kalpakas | 29 October 2021, 11:17:13 UTC | refactor(docs-infra): create `logSectionHeader()` helper in `deploy-to-firebase` script (#43963) Create a `logSectionHeader()` helper function to avoid duplicating code. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 50b2d27 | George Kalpakas | 29 October 2021, 11:17:13 UTC | refactor(docs-infra): convert `deploy-to-firebase` script to ESM (#43963) Convert the `deploy-to-firebase` script (and corresponding tests) from CommonJS format to ESM. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| c359da4 | George Kalpakas | 29 October 2021, 11:17:12 UTC | build(docs-infra): validate computed deployments in `deploy-to-firebase` script (#43963) The `deploy-to-firebase` script might have to deploy a single AIO build to multiple projects/sites (potentially with small tweaks between each). This commit adds a step to validate the computed deployments to ensure they are compatible with each other (for example, that there is exactly one primary deployment that builds the app and sets the theme/mode and that all secondary deployments are compatible with the primary one). PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 3f480a1 | George Kalpakas | 29 October 2021, 11:17:12 UTC | refactor(docs-infra): add `name` and `type` to deployment info (#43963) This commit adds two new properties, `name` and `type`, to deployment info data. This will make it easier to differentiate between deployment targets (e.g. primary vs secondary) and will provide more informative log messages. In a subsequent commit, this new data can be used to validate the computed deployments list. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 8292c66 | George Kalpakas | 29 October 2021, 11:17:12 UTC | fix(docs-infra): improve an error message in `deploy-to-firebase` script (#43963) This commit fixes a typo in an error message thrown in the `deploy-to-firebase` script (`but it was but it was` --> `but it was`). It also makes the error clearer when the request was not redirected. Old error: > Expected '<original-url>' to be redirected to '<expected-url>', but it > was but it was redirected to 'undefined'. New error: > Expected '<original-url>' to be redirected to '<expected-url>', but it > was not redirected. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 6ee479d | George Kalpakas | 29 October 2021, 11:17:12 UTC | build(docs-infra): enable linting for `deploy-to-firebase` scripts (#43963) This commit enables linting for the scripts in `aio/scripts/deploy-to-firebase/`. It also makes the necessary changes to the files to make linting pass. PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 2fa48e5 | George Kalpakas | 29 October 2021, 11:17:11 UTC | refactor(docs-infra): move `deploy-to-firebase.js` into a dedicated directory (#43963) This commit moves the `aio/scripts/deploy-to-firebase.js` script into a new directory, `aio/scripts/deploy-to-firebase/`. This will make it easier to break it up into multiple smaller files to better organize the code (without polluting the `aio/scripts/` directory). PR Close #43963 | 29 October 2021, 22:05:10 UTC |
| 96b99c4 | Alan Agius | 29 October 2021, 11:16:58 UTC | docs: update `creating libraries` guide (#43982) We update the `creating libraries` guide to remove View Engine references. This is because in version 13 users are no longer able to build libraries using View Engine. In addition to the above, we also remove references to `npm link`. As this is actually not a recommended workflow, and was mostly needed in older versions of the CLI prior to version 6, were multi-projects workspaces were introduced. Closes #43949 PR Close #43982 | 29 October 2021, 21:23:04 UTC |
| 3faef71 | George Kalpakas | 19 October 2021, 13:19:03 UTC | refactor(docs-infra): align docs examples with default CLI TS config (#43880) This commit enable the `noImplicitOverride` and `noPropertyAccessFromIndexSignature` TypeScript compiler options for docs examples to better align with the default configuration of new Angular CLI apps. It also makes the necessary changes to the docs examples source code. PR Close #43880 | 29 October 2021, 20:10:26 UTC |
| 12b7f44 | George Kalpakas | 19 October 2021, 13:19:03 UTC | build(docs-infra): update docs examples to Angular v13.0.0-rc.0 (#43880) This commit updates the docs examples to Angular v13.0.0-rc.0. In addition to updating the dependency versions, it also updates the projects' structure and configs to more closely match what a new v13 CLI app would look like. See, also, the [diff][1] between a basic v12.1.3 CLI app and a v13.0.0-rc.0 one. (NOTE: v12.1.3 was the last version for which we aligned the projects with how a new CLI app would look like.) Additionlly: - Since we now use RxJS v7 in docs examples, this commit removes the extra CI steps to explicitly test the docs examples against RxJS v7. - Since Angular v13 no longer supports IE, this commit removes an IE-specific section from `upgrade-setup.md`. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/12.1.3..13.0.0-rc.0 PR Close #43880 | 29 October 2021, 20:10:26 UTC |
| 620a705 | George Kalpakas | 19 October 2021, 13:19:03 UTC | test(docs-infra): fix `practical-observable-usage` docs example tests with RxJS v7 (#43880) Due to how `debounceTime()` works in RxJS v7, Jasmine's mock clock was not enough to trigger it. This commit fixes it by providing a similar mock clock that is able to mock all of `Date.now()`, `setInterval()` and `setTimeout()`. PR Close #43880 | 29 October 2021, 20:10:26 UTC |
| 6ff9798 | George Kalpakas | 19 October 2021, 13:19:02 UTC | build: use the latest version of Chrome (v93) in non-bazel tests (#43880) This commit updates the version of Chrome used in non-bazel tests (via Puppeteer) to the latest (v93). PR Close #43880 | 29 October 2021, 20:10:26 UTC |
| f225bfd | Jochen Kraushaar | 15 July 2021, 08:00:33 UTC | docs(common): describe behavior when reference changes (#42863) PR Close #42863 | 28 October 2021, 18:34:26 UTC |
| 8ae9982 | vthinkxie | 13 April 2021, 02:10:35 UTC | fix(core): support `InjectFlags` argument in `NodeInjector.get()` (#41592) The `InjectFlags` argument was defined for both `getOrCreateInjectable()` and `Injector`, but was ignored in `NodeInjector`. This PR adds support for getting parent token via `NodeInjector.get()`. close #31776 PR Close #41592 | 28 October 2021, 18:20:01 UTC |
| 59ca52f | Pete Bacon Darwin | 20 October 2021, 21:08:50 UTC | refactor: simplify the LOCALE_ID provider (#43913) Other parts of the intialization process are responsible for passing the locale id to ivy, so it does not need to happen in the provider factory. E.g. `PlatformRef.bootstrapModule()` and `R3TestBedCompiler.finalize()`. PR Close #43913 | 28 October 2021, 18:19:13 UTC |
| 4ba1a24 | Pete Bacon Darwin | 20 October 2021, 18:25:22 UTC | refactor: remove ɵloc and related code (#43913) This code is not used in ivy - and probably was not being used in View Engine either. PR Close #43913 | 28 October 2021, 18:19:13 UTC |
| 8d89b28 | Jessica Janiuk | 27 October 2021, 21:22:29 UTC | Revert "refactor(forms): update minlength/maxlength to inherit abstractValidator" (#43971) This reverts commit 7b31b887f96cbf2f6f93d13f0db4e312d8fac345. PR Close #43971 | 27 October 2021, 21:42:26 UTC |
| a2ce1da | Jessica Janiuk | 27 October 2021, 18:29:30 UTC | release: cut the v13.0.0-rc.2 release (#43968) | 27 October 2021, 18:29:30 UTC |
| 7de7dc8 | Mladen Jakovljević | 26 October 2021, 18:47:08 UTC | fix(docs-infra): fix heritage links (#43956) Fix incorrect escape of special characters when rendering member heritage docs. Example: DefaultIterableDiffer docs incorrectly renders what this class implements - it does not fully display generic types of implemented interfaces. PR Close #43956 | 27 October 2021, 16:13:36 UTC |
| b7be4cf | Virginia Dooley | 15 September 2021, 17:43:20 UTC | docs: review tag added (#43465) PR Close #43465 | 27 October 2021, 16:13:02 UTC |
| cfc509c | Alan Agius | 26 October 2021, 11:25:34 UTC | refactor(migrations): remove no longer accessible migrations (#43947) With this change we remove no longer needed migrations. These migrations are no longer accessible following a change angular/angular-cli#21986 in the Angular CLI. The CLI now shows an error message when users try to update `@angular/` and `@nguniversal/` packages across multiple major versions. Example to update from version 11 to version 13 the recommand approach is to run the following commands ``` ng update @angular/core@12 ng update @angular/core@13 (which is the same as ng update @angular/core) ``` NB: It is recommand that when update from one major to another, users verify that their applications is working as expected. PR Close #43947 | 26 October 2021, 23:59:42 UTC |
| ec23ae9 | Virginia Dooley | 17 September 2021, 16:20:52 UTC | docs: reviewed tag added (#43487) PR Close #43487 | 26 October 2021, 23:57:45 UTC |
| 0dbe1c6 | Virginia Dooley | 17 September 2021, 16:28:06 UTC | docs: reviewed tag added (#43488) PR Close #43488 | 26 October 2021, 22:57:21 UTC |
| 081a4c2 | Renovate Bot | 26 October 2021, 20:21:42 UTC | build: update all non-major dependencies (#43917) PR Close #43917 | 26 October 2021, 21:16:07 UTC |
| c44d1cb | iRealNirmal | 14 October 2021, 04:06:32 UTC | refactor(forms): update minlength/maxlength to inherit abstractValidator (#43835) 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 #43835 | 26 October 2021, 20:24:40 UTC |
| 97b6f68 | Joey Perrott | 25 October 2021, 22:50:44 UTC | ci: update commit-message-based-labels job to be called labels (#43944) Using the job name labels results in a more readable and better looking Github status. PR Close #43944 | 26 October 2021, 20:20:05 UTC |
| 1571c2b | Joey Perrott | 21 October 2021, 20:02:30 UTC | build: create issue selector configuration (#43923) Create a configuration file to set up the new issue selector page. PR Close #43923 | 26 October 2021, 20:19:07 UTC |
| 269fece | Renovate Bot | 25 October 2021, 21:27:24 UTC | build: lock file maintenance (#43937) PR Close #43937 | 26 October 2021, 20:12:01 UTC |
| fa7693f | JoostK | 02 October 2021, 20:09:17 UTC | refactor(compiler-cli): extract error documentation base url into separate file (#43527) Prior refactorings caused unexpected g3 sync issues due to a patch that changes the error documentation URL. This commit moves the base url into a separate file to make this more apparent. PR Close #43527 | 26 October 2021, 18:22:34 UTC |
| 8e13c35 | JoostK | 21 September 2021, 21:39:11 UTC | fix(compiler-cli): avoid broken references in .d.ts files due to @internal markers (#43527) The `ErrorCode` enum in the `error_code.ts` file is governed by public api guards but the other top-level exports from that file are exempt from public api documentation and are therefore marked as `@internal`. However, TypeScript is configured with the `stripInternal` compiler option such that declarations with `@internal` markers are not emitted into the `.d.ts` files, but this means that the reexports in the barrel file end up referring to missing declarations. The `stripInternal` option is considered internal and its documentation states to use at your own risk (as per https://github.com/microsoft/TypeScript/issues/45307). Having the option enabled is desirable for us as it works well for hiding class fields that are marked `@internal`, which is an effective way to hide members from the .d.ts file. As a workaround for the issue with top-level symbols, the declarations with `@internal` markers are moved to dedicated files for which no public api guard is setup, therefore allowing their `@internal` markers to be dropped. Fixes #43097 PR Close #43527 | 26 October 2021, 18:22:33 UTC |
| 59e56e7 | dirk diebel | 24 October 2021, 09:17:20 UTC | docs(docs-infra): change deprecated keyboardEvent.keyCode example to use keyboardEvent.code (#43934) PR Close #43934 | 26 October 2021, 00:05:23 UTC |
| 940eafa | amayer42 | 25 October 2021, 16:40:23 UTC | docs(localize): fix spelling of documentation link (#43941) Fixes the spelling of 'i18n' in a documentation link. PR Close #43941 | 25 October 2021, 22:05:18 UTC |
| 15bdd0d | Jessica Janiuk | 25 October 2021, 21:37:43 UTC | Revert "refactor(migrations): remove no longer accessible migrations" (#43943) This reverts commit f21ad8780b211f6fe0c3d9c80e3d85727c33685f. PR Close #43943 | 25 October 2021, 22:02:32 UTC |
| 087fae5 | Alan Agius | 25 October 2021, 18:11:45 UTC | refactor(migrations): remove no longer accessible migrations (#43942) With this change we remove no longer needed migrations. These migrations are no longer accessible following a change https://github.com/angular/angular-cli/pull/21986 in the Angular CLI. The CLI now shows an error message when users try to update `@angular/` and `@nguniversal/` packages across multiple major versions. Example to update from version 11 to version 13 the recommand approach is to run the following commands ``` ng update @angular/core@12 ng update @angular/core@13 (which is the same as ng update @angular/core) ``` NB: It is recommand that when update from one major to another, users verify that their applications is working as expected. PR Close #43942 | 25 October 2021, 19:32:27 UTC |
| 8277c38 | Andrew Kushnir | 23 October 2021, 19:46:07 UTC | test(platform-browser): complete component bootstrap before switching to the next test (#43933) The bootstrap tests that reused the same component (the `HelloRootCmp` one) were randomly failing due to the incomplete cleanup between tests. This commit ensures that the component bootstrap is fully cimpleted and there are no pending async actions before going to the next test. PR Close #43933 | 25 October 2021, 17:58:27 UTC |
| 7c5d642 | George Kalpakas | 23 October 2021, 09:41:42 UTC | fix(ngcc): support alternate UMD layout when adding new imports (#43931) In #43879, `UmdReflectionHost` was updated to deal with the new UMD format used by Rollup, where the parenthesis is around the wrapper function and not the wrapper function call. For reference, this caused failures in the `ngcc-validation` repo ([example 1][1], [example 2][2]). This commit updates `UmdRenderingFormatter` to also handle both UMD formats. In order to validate the change, this commit also updates the `UmdRenderingFormatter` tests to run against both UMD formats. [1]: https://circleci.com/gh/angular/ngcc-validation/65916 [2]: https://circleci.com/gh/angular/ngcc-validation/65758 PR Close #43931 | 25 October 2021, 17:56:27 UTC |
| 8178a30 | Doug Parker | 13 October 2021, 23:23:00 UTC | docs: deprecate `@angular-devkit/build-optimizer` (#43915) The entire package is deprecated in v13. Deprecation message is mostly copied from the package's [README](https://github.com/angular/angular-cli/blob/13.0.0-next.9/packages/angular_devkit/build_optimizer/README.md), with just some minor edits. (cherry picked from commit d81744e60018281e69f98c051e139f9336127b8e) PR Close #43915 | 25 October 2021, 17:54:52 UTC |
| 9968a8a | Alan Agius | 21 October 2021, 07:12:04 UTC | docs: remove fesm5 and esm5 deprecation notice. (#43915) This has been removed in version 11 and should no longer be listed. PR Close #43915 | 25 October 2021, 17:54:52 UTC |
| e569a9c | Alan Agius | 21 October 2021, 07:06:20 UTC | docs: update CLI deprecation guide to reflect new deprecations (#43915) With this change we update the CLI deprecations sections as per version 13. PR Close #43915 | 25 October 2021, 17:54:52 UTC |
| 096ebb2 | Alan Agius | 21 October 2021, 06:48:31 UTC | docs: format tables in deprecations page (#43915) Currently, the table are unformatted which makes it extremely hard to read when viewing the markdown file directly. PR Close #43915 | 25 October 2021, 17:54:52 UTC |
| 97fc9de | ericcheng2005 | 02 October 2021, 19:46:28 UTC | refactor(core): made comment structure consistent in index.ts (#43684) changed second big block of comments to use multi-line comment structure instead of multiple single-line comments PR Close #43684 | 21 October 2021, 18:40:00 UTC |
| 6dc4d83 | ericcheng2005 | 02 October 2021, 19:39:40 UTC | docs: added commas to sentences in .vscode/README.md (#43684) PR Close #43684 | 21 October 2021, 18:40:00 UTC |
| 23928a0 | ericcheng2005 | 02 October 2021, 19:29:45 UTC | docs: fixed minor grammar mistakes in CONTRIBUTING (#43684) PR Close #43684 | 21 October 2021, 18:39:59 UTC |
| 72f6877 | Doug Parker | 15 October 2021, 19:12:45 UTC | docs: remove Ivy-specific guides (#43860) Ivy is the only supported rendering engine in v13, so there is no need to document the concept. Everything in Angular is Ivy. This starts the removal process by deleting Ivy-specific guides and references to them. It also updates the glossary to be more clear that Ivy is the current rendering engine while View Engine is simply a historical note. This does not attempt to fully remove all references to "Ivy" or "View Engine", that will likely be a more involved clean up process. PR Close #43860 | 21 October 2021, 18:14:34 UTC |
| adc68b1 | krzysztof-grzybek | 10 October 2021, 09:54:16 UTC | fix(router): reuse route strategy fix (#43791) Currently, it's impossible to cache (detach/attach) parent route without caching child routes. This produces a bug, when navigating from a/b to c, then to a/d, where a route is cached. On the last navigation, we incorrectly restore a/b route instead of a/d. This change introduces new behavior: if the route should be detached/attached, we do so, but we check also child routes recursively. Fixes #17333 PR Close #43791 | 21 October 2021, 16:28:03 UTC |
| 5d03184 | Alan Agius | 20 October 2021, 11:22:06 UTC | ci: update `angular/dev-infra/github-actions` sha (#43904) Consume latest version of `angular/dev-infra/github-actions`. PR Close #43904 | 21 October 2021, 16:26:36 UTC |
| bbbf678 | Alan Agius | 20 October 2021, 11:19:32 UTC | ci: replace `breaking-changes-label` with `commit-message-based-labels` (#43904) See: https://github.com/angular/dev-infra/pull/269 for more context PR Close #43904 | 21 October 2021, 16:26:35 UTC |
| 22009f6 | Tomasz Domański | 21 October 2021, 08:35:19 UTC | docs: fix typos in the workspace config guide (#43918) PR Close #43918 | 21 October 2021, 14:42:46 UTC |
| 0039b71 | George Kalpakas | 05 October 2021, 17:14:15 UTC | refactor(service-worker): avoid unnecessary writes to cache when version fails (#43680) When an app version is detected as broken, the SW calls the `Driver#versionFailed()` method. Previously, this method would in turn call the `Driver#sync()` method, which writes some metadata about the SW's state to the `ngsw:/:db:contol` cache. More specifically, `Driver#sync()` persists info about all known app versions, which one is the latest and also what version each client is assigned to. However, no relevant info is changed inside `Driver#versionFailed()`, so the call to `Driver#sync()` is redundant (since there are no changes that need to be synced with the cache). This is a left-over from before #43518, when `Driver#versionFailed()` used to update version assignments and thus did require synchronization with the cache. This commit removes the redundant `Driver#sync()` call to avoid an unnecessary write to the cache. PR Close #43680 | 21 October 2021, 14:20:51 UTC |
| 665466d | iRealNirmal | 04 October 2021, 13:05:34 UTC | docs: move deprecations example snippets to external file (#43700) Moving angular depreciation examples to external project closes #43337 PR Close #43700 | 20 October 2021, 20:24:55 UTC |
| ae52bf1 | Willy Schott | 19 October 2021, 14:34:00 UTC | docs: clarify meaning of ellipsis in bazel command (#43890) PR Close #43890 | 20 October 2021, 20:14:49 UTC |
| b31a9a7 | Andrew Kushnir | 20 October 2021, 16:57:26 UTC | release: cut the v13.0.0-rc.1 release (#43911) | 20 October 2021, 16:57:26 UTC |
| 7d33af0 | JoostK | 19 October 2021, 20:36:00 UTC | test(compiler-cli): run i18n extraction tests using Ivy compiler (#43893) This commit re-enables the `extract_i18n` test target and updates the test to run with the Ivy compiler. PR Close #43893 | 19 October 2021, 23:26:22 UTC |
| aef0138 | JoostK | 19 October 2021, 17:24:15 UTC | test(compiler-cli): run watch mode tests using Ivy compiler (#43893) This commit re-enables the `perform_watch` test target and updates the test to run with the Ivy compiler. Additionally, this target was switched over to use Angular v12 packages as input to the test, to allow the ViewEngine tests to continue working with v13 packages which are Ivy-only. This commit reverts those changes now that View Engine tests are disabled, as it's desirable to test against local artifacts that are build within the monorepo instead of depending on NPM packages. PR Close #43893 | 19 October 2021, 23:26:22 UTC |
| 9d9346c | Alan Agius | 14 October 2021, 16:59:35 UTC | docs: add docs about build cache (#43843) With this change we add docs about persistant disk cache with was enabled by default in the CLI via https://github.com/angular/angular-cli/pull/21827 PR Close #43843 | 19 October 2021, 17:45:30 UTC |
| 812a33d | Joey Perrott | 15 October 2021, 21:40:58 UTC | ci: mark core/schematics/test:test and compiler-cli/test:perform_watch test as view engine only (#43862) Both test targets fail because, at test time, they use the view engine compiler, even when bazel sets the configuration to use ivy. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| aafde79 | Doug Parker | 15 October 2021, 17:14:23 UTC | refactor(compiler-cli): throw an error when compiling with View Engine. (#43862) The View Engine compiler now throws when constructed and will be removed shortly. Direct users should switch to `NgtscProgram` to build with [Ivy](https://angular.io/guide/ivy). The View Engine compiler is being removed, so this makes it throw an error to ensure no one accidentally depends on code being removed. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| 57bf6b7 | Joey Perrott | 15 October 2021, 21:19:18 UTC | ci: correct comment related to building view engine npm packages (#43862) Removing the comment related about building the npm packages using view engine as it was actually done via ivy, now that ivy is used for all builds there is no need for expressing the aspect of the build. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| 5e562b6 | Joey Perrott | 15 October 2021, 21:09:44 UTC | ci: remove view engine test job (#43862) Remove the view engine test job as view engine is no longer being tested on CI. Additionally, update size tracking to rely on test job instead of test_ivy_aot. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| 04b4209 | Joey Perrott | 15 October 2021, 21:06:15 UTC | ci: remove windows view engine test job (#43862) Remove the windows view engine test job as view engine is no longer being tested on CI. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| f1e1849 | Joey Perrott | 15 October 2021, 20:45:56 UTC | ci: remove saucelabs view engine tests (#43862) Remove the view engine specific saucelabs test job and associated tags/tooling as view engine is no longer being tested on CI. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| 442f520 | Joey Perrott | 15 October 2021, 21:02:52 UTC | build: remove ivy-aot bazel tag (#43862) Remove the ivy-aot bazel tag from usage as it served a duplicate purpose as ivy-only which is now removed as both are unneeded with Ivy as the default compiler used. PR Close #43862 | 19 October 2021, 17:06:57 UTC |
| 90ac770 | Joey Perrott | 15 October 2021, 21:00:18 UTC | build: remove fixme-ivy-aot tag filter (#43862) Remove the fixme-ivy-aot tag filter from usage as no targets are tagged with fixme-ivy-aot as ivy is now the compiler used by default. PR Close #43862 | 19 October 2021, 17:06:56 UTC |
| 959f563 | Joey Perrott | 15 October 2021, 20:58:45 UTC | build: remove "ivy-only" bazel tag (#43862) Because all actions are assumed to be running on Ivy, things which only work on Ivy should not be marked as Ivy only. PR Close #43862 | 19 October 2021, 17:06:56 UTC |
| 730511b | Joey Perrott | 15 October 2021, 20:27:17 UTC | build: rename "no-ivy-aot" tag to "view-engine-only" (#43862) Using the tag "view-engine-only" better describes the expected usage of bazel targets with the test. They can only be run with view engine. PR Close #43862 | 19 October 2021, 17:06:56 UTC |
| c3f677d | Joey Perrott | 15 October 2021, 20:26:15 UTC | build: remove test-ivy-aot yarn script (#43862) Since building with ViewEngine is not longer desired on CI, removing the ivy vs non-ivy testing yarn scripts is done, informing developers to instead use `yarn test` as all tests should be run using the Ivy complier. PR Close #43862 | 19 October 2021, 17:06:56 UTC |
| b75ee8d | Joey Perrott | 15 October 2021, 20:22:30 UTC | build: Use Ivy compiler for bazel builds by default (#43862) Setting the angular_ivy_enabled environment variable to True will default Bazel builds to use the Ivy compiler rather than defaulting to ViewEngine. PR Close #43862 | 19 October 2021, 17:06:56 UTC |
| b489ae5 | Joey Perrott | 18 October 2021, 18:27:43 UTC | ci: remove browserstack configuration (#43881) Remove browserstack configuration from the repo as it is not used for our CI. PR Close #43881 | 18 October 2021, 22:00:23 UTC |
| c882b9f | Pete Bacon Darwin | 18 October 2021, 16:24:21 UTC | fix(ngcc): support alternate wrapper function layout for UMD (#43879) Recently rollup, used by ng-packagr, changed the position of parentheses around its generated UMD wrapper functions. This commit ensures that ngcc can handle both. Fixes #43870 PR Close #43879 | 18 October 2021, 21:57:03 UTC |
| fc6519c | Andrew Kushnir | 18 October 2021, 19:42:00 UTC | Revert "fix(compiler): support i18n interpolated only attribute bindings (#43815)" (#43882) This reverts commit bba0a8705548f16b4db3b88d03deb6e67a85e414. The reason for rollback: this change is breaking some targets in Google's codebase when there is no attribute value is displayed (attr.aria-label) when translated. PR Close #43882 | 18 October 2021, 20:16:01 UTC |
| 14b492d | Kristiyan Kostadinov | 18 October 2021, 10:56:52 UTC | fix(compiler): do not error if $any is used inside a listener (#43866) Fixes that `$any` casts weren't being converted to statements inside listeners which resulted in a compiler error. Fixes #43841. PR Close #43866 | 18 October 2021, 17:43:03 UTC |
| cbde9ed | George Kalpakas | 18 October 2021, 15:21:58 UTC | docs: fix a couple of random typos (#43878) PR Close #43878 | 18 October 2021, 17:41:34 UTC |
| dc6909a | Andrew Scott | 15 October 2021, 17:29:25 UTC | fix(router): Do not clear currentNavigation if already set to next one (#43852) Experimentation with the Router URL management exposed a situation where the `currentNavigation` was being cleared in the `finalize` after the `currentNavigation` was already set to the next one. This change ensures that the `currentNavigation` is only cleared if the id of the finalized transition matches the one on the `currentNavigation` object. PR Close #43852 | 18 October 2021, 17:30:54 UTC |
| dbcc4be | Andrew Scott | 28 September 2021, 23:34:45 UTC | refactor(router): Remove use of browserUrlTree in scheduleNavigation (#43632) There are no added tests here because the change is generally equivalent to what was there before. The goal of that piece of code is to prevent duplicate navigations due to the location synchronization code between AngularJS and Angular. That is, the Angular router listens to the `popstate` event and triggers navigations, but so does the AngularJS router and triggers navigations through `router.navigateByUrl`. The `setTimeout` in the Angular Router's `setUpLocationChangeListener` is there to make this bit of code work: the 'popstate'/'hashchange' navigation will necessarily come after the imperative nav triggered by AngularJS's location sync. Anyhow, in the long run, I would like to get rid of this bit of code altogether. We should not have special handling for these cases. The AngularJS/Angular location sync should either: 1. Not trigger a duplicate navigation in the first place or 2. Be tolerant to processing the duplicate navigation. In the short term, this change benefits the router while we investigate removing this logic completely because now browserUrlTree has a single responsiblity: to support `onSameUrlNavigation==='reload'`. This means that we can work towards removing the `browserUrlTree` tracking from the Router code at some point as well and have the `onSameUrlNavigation` logic be part of a pre-navigation hook that can be handled outside the `Router`. This may or may not be possible, but the change here opens up that change for investigation. PR Close #43632 | 18 October 2021, 17:29:23 UTC |
| db57e39 | David Shevitz | 18 October 2021, 05:44:06 UTC | docs: update getting started links to provide a more consistent user experience (#43872) PR Close #43872 | 18 October 2021, 16:25:36 UTC |
| 8c91e33 | Pete Bacon Darwin | 12 October 2021, 16:29:12 UTC | fix(compiler): support i18n interpolated only attribute bindings (#43815) While fully dynamic bound properties (and attributes) cannot be marked for localization, properties that only contain interpolation can. This commit ensure that attribute bindings that only contain interpolation can also be marked for localization. Closes #43260 PR Close #43815 | 18 October 2021, 16:24:42 UTC |
| ebc9b55 | dario-piotrowicz | 15 October 2021, 19:00:55 UTC | fix(docs-infra): add paddings to docs-card titles (#43859) improve the aio docs-card title by adding some padding so that it doesn't get too close to the card's edges PR Close #43859 | 18 October 2021, 16:23:19 UTC |
| 017748c | dario-piotrowicz | 16 October 2021, 21:35:41 UTC | fix(docs-infra): move security anchors outside callout elements (#43865) two callout elements in the security guide have anchors as their first child element instead of the callout's header causing ugly/unwanted spacing, move the anchors above the callout elements to fix such issue PR Close #43865 | 18 October 2021, 16:22:39 UTC |
| ee2678c | Paul Gschwendtner | 14 October 2021, 14:57:53 UTC | build: update bazel integration test to `rules_nodejs` v4.4.1 (#43853) Updates the Bazel integration test to `rules_nodejs` v4.4.1. Renovate could not complete this update automatically because it is unable to update the `package.json` and `lock` file due to there being relative `file:` references. PR Close #43853 | 15 October 2021, 20:55:53 UTC |
| 0983eec | Renovate Bot | 14 October 2021, 08:52:51 UTC | build: update all non-major dependencies (#43853) Updates all non-major dependencies to their latest available versions. PR Close #43853 | 15 October 2021, 20:55:53 UTC |
| 70c14ed | Pete Bacon Darwin | 15 October 2021, 16:48:26 UTC | build(docs-infra): add a box around CLI command line reference syntax (#43850) This commit helps to make the section that describes an overview of the syntax of a CLI command stand out from the surrounding text. Closes #26574 PR Close #43850 | 15 October 2021, 18:35:47 UTC |
| 772e08d | Andrew Scott | 14 October 2021, 16:44:31 UTC | fix(router): fix Router's public API for canceledNavigationResolution (#43842) The commit which made the `canceledNavigationResolution` property on the `Router` public did not add the corresponding configuration in the `ExtraOptions`. https://github.com/angular/angular/commit/3c6b653089837459809a370ebcaf8911c3bab9ed This was a mistake and is being corrected in this commit. We should not encourage changing the properties post-setup (i.e. `inject(Router).canceledNavigationResolution = 'computed'`). This manner of configuration makes the options non-tree shakeable because we have to keep both implementations in case the value changes at runtime. PR Close #43842 | 15 October 2021, 18:35:02 UTC |
| 12dfc0e | Younes Jaaidi | 05 October 2021, 15:35:49 UTC | docs: add younes jaaidi to GDE resources (#43721) PR Close #43721 | 15 October 2021, 17:49:26 UTC |
