Skip to main content

Browse the archive

https://github.com/angular/angular
19 April 2024, 08:24:33 UTC
sort by:
Revision Author Date Message Commit Date
cbf96c1 Alex Rickabaugh 03 November 2021, 20:45:25 UTC release: cut the v13.1.0-next.0 release (#44040) PR Close #44040 03 November 2021, 20:46:46 UTC
1cbe864 Alex Rickabaugh 03 November 2021, 20:33:15 UTC docs: release notes for the v12.2.13 release (#44039) PR Close #44039 03 November 2021, 20:39:31 UTC
1a1dfab Alex Rickabaugh 03 November 2021, 18:03:25 UTC docs: release notes for the v13.0.0 release (#44034) PR Close #44034 03 November 2021, 18:05:12 UTC
8d308dc 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:43 UTC
3fada9e 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:43 UTC
0cab229 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:43 UTC
3574e7d George Kalpakas 02 November 2021, 16:37:59 UTC build(docs-infra): update Angular CLI/framework/Material to final v13 RCs in docs examples (#43583) 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 #43583 03 November 2021, 00:31:58 UTC
763905b Paul Gschwendtner 29 October 2021, 15:55:17 UTC test: update size goldens for AIO after updating to final v13 RCs (#43583) 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 #43583 03 November 2021, 00:31:58 UTC
ac8b5bf Paul Gschwendtner 29 October 2021, 15:14:59 UTC build(docs-infra): update AIO to angular framework/components/cli final RCs (#43583) 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 #43583 03 November 2021, 00:31:58 UTC
08234f9 Renovate Bot 25 October 2021, 17:11:39 UTC build: update angular (#43583) PR Close #43583 03 November 2021, 00:31:58 UTC
fd1e7d4 Alex Rickabaugh 02 November 2021, 02:00:35 UTC docs: release notes for the v13.0.0-rc.3 release (#44012) PR Close #44012 02 November 2021, 02:02:24 UTC
509b145 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
1f8d5c3 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:53 UTC
32fa533 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
d015ac2 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
3d1ac6a 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:32 UTC
73b35af 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:32 UTC
fe4bceb 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:32 UTC
19b2d6d 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:32 UTC
9316254 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:32 UTC
13f6243 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:32 UTC
98912bf 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:32 UTC
557cabc 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:32 UTC
8cded17 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:32 UTC
fc3cd38 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:32 UTC
408e4da 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:06 UTC
6e32fa2 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:33 UTC
4b4996f 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:32 UTC
a72333c 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:49 UTC
a01e02d 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:44:58 UTC
df5f737 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:44:58 UTC
6247efa 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:55 UTC
64335eb 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:55 UTC
619b7cc 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:55 UTC
9867a5d 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:55 UTC
b322585 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:55 UTC
967283e 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
8d8cdc1 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:04 UTC
b202539 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:04 UTC
be24bb7 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:04 UTC
cd35925 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:03 UTC
02971ab 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:03 UTC
ea67651 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:03 UTC
4f39c2b 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:03 UTC
cbd0b37 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:03 UTC
23b7543 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:02 UTC
b16a92d 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:02 UTC
ce51f99 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:02 UTC
5a21519 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:02 UTC
4f4b2b5 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:02 UTC
80d8eb8 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:02 UTC
3894cef 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:02 UTC
f1b4048 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:02 UTC
2baadb9 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:02 UTC
f8ab6e9 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:02 UTC
6b8cdc9 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:03 UTC
7b35a34 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:25 UTC
8286190 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:25 UTC
0fc4e66 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:25 UTC
bc5e295 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:25 UTC
e3511e2 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:23 UTC
65cb2c5 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:19:58 UTC
c315878 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:12 UTC
70d3805 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:12 UTC
17be47e 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
a84983e Jessica Janiuk 27 October 2021, 18:36:50 UTC docs: release notes for the v13.0.0-rc.2 release (#43969) 27 October 2021, 18:36:50 UTC
96944eb Jessica Janiuk 27 October 2021, 18:26:30 UTC docs: release notes for the v12.2.12 release (#43967) 27 October 2021, 18:26:30 UTC
b393188 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:34 UTC
aa55563 Virginia Dooley 15 September 2021, 17:43:20 UTC docs: review tag added (#43465) PR Close #43465 27 October 2021, 16:13:01 UTC
57cbb4f 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
e2f9dcf Paul Gschwendtner 26 October 2021, 13:45:58 UTC ci: update commit for components-repo-unit-tests job (#43932) Updates the SHA for the components-repo-unit-tests job. Due to us enabling code splittign in the Angular compiler CLI package, the postinstall patches in Angular Components started failing. The latest commit of Angular Components no longer patches any JS files of the compiler-cli, so updating the job unblocks us from enabling code splitting within ESBuild. PR Close #43932 26 October 2021, 23:58:27 UTC
a3908bd Paul Gschwendtner 23 October 2021, 15:47:21 UTC build: enable code splitting for esbuild bundling of localize tools (#43932) Enables code spitting for ESBuild bundling of the localize/tools entry point. When we initially configured ESBuild as part of APF v13, we left this option disabled as code splitting is marked experimental. The ESM splitting mechanism in ESBuild seems very solid so far (judging subjectively and by experience/reports in the ESBuild repo), so we should give it a shot, in order to significantly reduce the size of the NPM package, and simplify debugging (by not having duplicated code portions for all the different entry points). To clarify: Code splitting is helpful as we have multiple entry-points that currently duplicate code. With code splitting these entry-points would share common code instead. PR Close #43932 26 October 2021, 23:58:27 UTC
4b641a9 Paul Gschwendtner 23 October 2021, 15:47:21 UTC build: enable code splitting for esbuild bundling of compiler-cli (#43932) Enables code spitting for ESBuild bundling of the compiler-cli. When we initially configured ESBuild as part of APF v13, we left this option disabled as code splitting is marked experimental. The ESM splitting mechanism in ESBuild seems very solid so far (judging subjectively and by experience/reports in the ESBuild repo), so we should give it a shot, in order to significantly reduce the size of the NPM package, and simplify debugging (by not having duplicated code portions for all the different entry points). To clarify: Code splitting is helpful as we have multiple entry-points that currently duplicate code. With code splitting these entry-points would share common code instead. PR Close #43932 26 October 2021, 23:58:27 UTC
82b668a Virginia Dooley 17 September 2021, 16:20:52 UTC docs: reviewed tag added (#43487) PR Close #43487 26 October 2021, 23:57:43 UTC
284f585 Virginia Dooley 17 September 2021, 16:28:06 UTC docs: reviewed tag added (#43488) PR Close #43488 26 October 2021, 22:57:19 UTC
6c47139 Renovate Bot 26 October 2021, 20:21:42 UTC build: update all non-major dependencies (#43917) PR Close #43917 26 October 2021, 21:16:06 UTC
5c22dfe 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
5d66b4a 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:03 UTC
143bb9f 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:06 UTC
58beafb Renovate Bot 25 October 2021, 21:27:24 UTC build: lock file maintenance (#43937) PR Close #43937 26 October 2021, 20:12:00 UTC
28a40f3 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:32 UTC
5d678de 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:32 UTC
a91fe6d 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:22 UTC
0e05f64 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:17 UTC
0873ae2 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
0b4350c 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
bf1a2fc 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:25 UTC
6e37c93 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:26 UTC
786f02b Renovate Bot 23 October 2021, 05:42:26 UTC build: update dependency eslint-plugin-jsdoc to v37 (#43930) PR Close #43930 25 October 2021, 17:55:54 UTC
be564e6 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
e48b499 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
a3af9b1 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
9b240c7 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
b1c0286 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:39:58 UTC
2e941d2 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:39:58 UTC
2189c10 ericcheng2005 02 October 2021, 19:29:45 UTC docs: fixed minor grammar mistakes in CONTRIBUTING (#43684) PR Close #43684 21 October 2021, 18:39:58 UTC
4ed8dc8 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
45e4e60 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
643cdf7 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:34 UTC
a1d44d9 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:34 UTC
back to top