https://github.com/angular/angular

sort by:
Revision Author Date Message Commit Date
f148751 release: cut the v16.0.0-next.7 release 06 April 2023, 02:57:53 UTC
a747954 docs: release notes for the v15.2.6 release 06 April 2023, 02:46:21 UTC
40ed152 refactor(animations): remove #9100 todos. (#49407) Breaking change: On `AnimationPlayer.setPosition` the argument is now of type `number` PR Close #49407 06 April 2023, 02:33:52 UTC
9bd9a11 refactor(platform-browser): remove deprecated `BrowserTransferStateModule` symbol (#49718) The `TransferState` class was updated in v14 in a way that the `BrowserTransferStateModule` was no longer required. The `BrowserTransferStateModule` was deprecated in v14.1 and it's currently empty. This commit removes the `BrowserTransferStateModule`. BREAKING CHANGE: The deprecated `BrowserTransferStateModule` was removed, since it's no longer needed. The `TransferState` class can be injected without providing the module. The `BrowserTransferStateModule` was empty starting from v14 and you can just remove the reference to that module from your applications. PR Close #49718 05 April 2023, 20:00:25 UTC
dc9651b refactor(platform-browser): remove empty `begin` and `end` methods from renderer (#49630) This methods are optional and thus not needed to be defined. PR Close #49630 05 April 2023, 18:42:57 UTC
d37e21c refactor(animations): remove Domino specific logic (#49630) These workarounds are no longer required following the fixes in https://github.com/angular/domino/pull/14/ PR Close #49630 05 April 2023, 18:42:57 UTC
4f3abbc refactor(platform-server): remove `ServerRendererFactory2` and `EmulatedEncapsulationServerRenderer2` (#49630) These methods are no longer required following the fixes in https://github.com/angular/domino/pull/14/ PR Close #49630 05 April 2023, 18:42:57 UTC
42f2f41 refactor(platform-browser): update renderer to be able to remove `ServerRendererFactory2` and `EmulatedEncapsulationServerRenderer2` (#49630) This commits updates the render to able to handle the slight differences between platform-server and platform-browser. This is needed to eventually be able to remove `ServerRendererFactory2` and `EmulatedEncapsulationServerRenderer2` from platform-server. PR Close #49630 05 April 2023, 18:42:57 UTC
a6fc8b3 refactor(core): add explicit import for ngDevMode (#49708) This commit adds an explicit import of the ngDevMode definition to the files in the signal package which use it. PR Close #49708 05 April 2023, 18:10:09 UTC
a4732c6 refactor(core): export additional symbols from the signals index (#49708) This commit adds a few missing exports from the signals index. PR Close #49708 05 April 2023, 18:10:09 UTC
1079528 refactor(core): add `postSignalSetFn` hook for `WritableSignal` (#49708) This commit adds a hook to `WritableSignal` that is called whenever the signal's value is updated via the mutation API. This hook allows consumers to implement logic which is synchronous with signal sets (e.g. executing effects). It's currently unused. PR Close #49708 05 April 2023, 18:10:09 UTC
77bdf77 build: combine `@bazel/concatjs` patches (#49714) This commit combines all the `@bazel/concatjs` patches PR Close #49714 05 April 2023, 17:54:29 UTC
1c16be4 build: update domino digest to aa8de34 (#49716) See associated pull request for more information. PR Close #49716 05 April 2023, 17:52:49 UTC
df1dfc4 fix(core): make sure that lifecycle hooks are not tracked (#49701) Angular lifecycle hooks should never be run as part of the reactive context: we do not expect that signal reads in lifecycle hooks report to any consumers. In the current Angular some of the lifecycle hooks can be flushed early, while executting template update pass. We need to make sure that signal reads in those lifecycle hooks do not register as part of the effect that marks components for check. " PR Close #49701 05 April 2023, 17:48:22 UTC
a4e749f fix(core): When using setInput, mark view dirty in same was as `markForCheck` (#49711) `ComponentRef.setInput` internally calls `markDirtyIfOnPush` which only marks the given view as dirty but does not mark parents dirty like `ChangeDetectorRef.markForCheck` would. https://github.com/angular/angular/blob/f071224720f8affb97fd32fb5aeaa13155b13693/packages/core/src/render3/instructions/shared.ts#L1018-L1024 `markDirtyIfOnPush` has an assumption that it’s being called from the parent’s template. That is, we don’t need to mark dirty to the root, because we’ve already traversed down to it. The function used to only be called during template execution for input bindings but was added to `setInput` later. It's not a good fit because it means that if you are responding to events such as an emit from an `Observable` and call `setInput`, the view of your `ComponentRef` won't necessarily get checked when change detection runs next. If this lives inside some `OnPush` component tree that's not already dirty, it only gets refreshed if you also call `ChangeDetectorRef.markForCheck` in the host component (because it will be "shielded" be a non-dirty parent). PR Close #49711 05 April 2023, 17:13:21 UTC
aad05eb feat(core): support usage of non-experimental decorators with TypeScript 5.0 (#49492) Previously, attempting to turn off the `experimentalDecorators` TypeScript configuration option within an Angular project would result in build time errors. These errors were due to an exposed Decorator signature from `@angular/core` that TypeScript thought was incompatible with standard decorators. However, Angular's class decorators (`Component`, `Directive`, `Pipe`, `Injectable`, `NgModule`) are actually already compatible with standard decorators. The export types for the decorators only needed to be updated to reflect that compatibility. With the updated exported types, applications will now successfully compile and execute in AOT mode with one important dependency injection caveat explained in the note below. For JIT mode applications that are built with the Angular CLI, `@ngtools/webpack`, or use `tsickle`, there were also no additional changes required. These tools automatically convert property decorators (now called field decorators) at build time to store Angular property metadata directly on the relevant class. Building with these tools is the overwhelmingly common method of building an application. Any applications that do not use one of these tools will not function at runtime in JIT mode if using standard decorators. The behavior and code for when experimental decorators is enabled has been left intact. NOTE: Angular constructor dependency injection that requires parameter decorators is not supported. The standard decorator specification does not support parameter decorators. The `inject` function must be used for all cases that previously required a parameter decorator. This includes such decorators as `Inject`, `Optional`, `Self`, `SkipSelf`, `Host`, and `Attribute`. Constructor dependency injection that relies only on the supplied parameter type will continue to function as expected if using AOT; as well as in JIT mode if using the Angular CLI, `@ngtools/webpack` directly, or `tsickle`. Documentation for the `inject` function can be found at: https://angular.io/api/core/inject The decorator specification proposal can be found at: https://github.com/tc39/proposal-decorators PR Close #49492 05 April 2023, 16:59:07 UTC
d497be7 refactor(core): Use the nullish coalescing assignment in render3 functions (#49698) The usage of `??=` make the code more clear & concise. PR Close #49698 05 April 2023, 16:45:53 UTC
136ffbc refactor(forms): Add a test that uses ControlConfig with a non-static validator. (#49693) Previously, this PR cleaned up a bug introduced by #48679. However, since that PR needed to be rolled back, this PR now just checks in the test, to prevent that issue from re-occurring in the future. PR Close #49693 05 April 2023, 16:08:39 UTC
3b863dd refactor(core): Remove `ReflectiveInjector` symbol (#48103) The `ReflectiveInjector` symbol has been deprecated in v5 (11 major versions ago). This commit removes ReflectiveInjector and related symbols. BREAKING CHANGE: The `ReflectiveInjector` and related symbols were removed. Please update the code to avoid references to the `ReflectiveInjector` symbol. Use `Injector.create` as a replacement to create an injector instead. PR Close #48103 04 April 2023, 23:43:53 UTC
f071224 build: update eslint dependencies to v5.57.1 (#49696) See associated pull request for more information. PR Close #49696 04 April 2023, 22:14:32 UTC
1aef29c refactor(core): Cleanup for Iterable differs test. (#49598) Remove some `any` and use the non-deprecated `Injector.create` overload. PR Close #49598 04 April 2023, 22:13:01 UTC
061f3d1 feat(core): Drop public `factories` property for `IterableDiffers` : Breaking change (#49598) The `factories` property was marked as deprecated in v4 to make it private. Let's move it to private. PR Close #49598 04 April 2023, 22:13:01 UTC
34b2d34 refactor(router): Remove RouterTestingModule in favor of RouterModule.forRoot (#49427) `RouterTestingModule` is not needed as of v16. Instead, TestBed automatically provides `MockPlatformLocation` in order to help test navigations in the application. The location mocks in the RouterTestingModule aren't necessary anymore. There doesn't appear to be any real documentation around `RouterTestingModule` other than the API docs. PR Close #49427 04 April 2023, 22:12:33 UTC
1f3f564 refactor(zone.js): remove #9100 todos. (#49409) This commit assigns the correct type instead of `any`. PR Close #49409 04 April 2023, 22:10:58 UTC
d71cde8 refactor(core): remove `ɵmakeDecorator` from private exports (#49300) `makeDecorator` is unused outside of core and is not part of the public API (not exported). PR Close #49300 04 April 2023, 22:10:16 UTC
b203e4c fix(router): create correct URL relative to path with empty child (#49691) The previous fix for squashing empty children didn't quite work when the existing route had segments. The result would be that the segments from the existing route were dropped from the final URL. PR Close #49691 04 April 2023, 22:05:41 UTC
a218ef5 build: update domino digest to 89bec1a (#49703) See associated pull request for more information. PR Close #49703 04 April 2023, 22:04:50 UTC
81e7d15 feat(platform-browser): enable HTTP request caching when using `provideClientHydration` (#49699) This commit adds support by default for HTTP caching when using `provideClientHydration`. Users can opt-out of this behaviour by using the `withoutHttpTransferCache` feature. ```ts import { bootstrapApplication, provideClientHydration, withNoHttpTransferCache, } from '@angular/platform-browser'; // ... bootstrapApplication(RootCmp, { providers: [provideClientHydration(withNoHttpTransferCache())] }); ``` PR Close #49699 04 April 2023, 22:04:03 UTC
41992a2 refactor(core): remove #9100 todos. (#49408) This commit includes a change on the `ViewRef.onDestroy` signature. PR Close #49408 04 April 2023, 22:01:48 UTC
b35fa73 feat(core): change the URL sanitization to only block javascript: URLs (#49659) In modern browsers, the 'javascript:' URL scheme is the only scheme that can execute JavaScript when passed in a navigation URL context (e.g. `a.href` value). Validate URL shemes to only contain characters allowed in the URL specification ([a-zA-Z-+.]), and that are not javascript (case insensitive). This is not a breaking change. The URL sanitization is loosen. PR Close #49659 04 April 2023, 22:01:13 UTC
f0978ad docs: fix typo (#49704) PR Close #49704 04 April 2023, 22:00:38 UTC
cb23864 docs: update Universal guide with hydration information (#49694) This commit updates the Universal guide with hydration-related information. Also, this commit updates the content to introduce a sequence of steps to enable SSR (previously it was hard to follow the information flow of the document). PR Close #49694 04 April 2023, 20:18:19 UTC
e7463dc docs: tweak hydration guide from feedback (#49705) This adds a few details based on feedback from the previous PR. PR Close #49705 04 April 2023, 20:17:54 UTC
edc3bb1 Revert "feat(forms): Improve typings form (async)Validators" (#49706) This reverts commit da189dec8ff2938ad3b065d79872555f3f15a44e. PR Close #49706 04 April 2023, 18:26:04 UTC
761e02d feat(platform-browser): add a public API function to enable non-destructive hydration (#49666) This commit adds the `provideClientHydration` function to the public API. This function can be used to enable the non-destructive Angular hydration. Important note: the non-destructive hydration feature is in Developer Preview mode, learn more about it at https://angular.io/guide/releases#developer-preview. Before you can get started with hydration, you must have a server side rendered (SSR) application. Follow the [Angular Universal Guide](https://angular.io/guide/universal) to enable server side rendering first. Once you have SSR working with your application, you can enable hydration by visiting your main app component or module and importing `provideClientHydration` from `@angular/platform-browser`. You'll then add that provider to your app's bootstrapping providers list. ```typescript import { bootstrapApplication, provideClientHydration, } from '@angular/platform-browser'; // ... bootstrapApplication(RootCmp, { providers: [provideClientHydration()] }); ``` Alternatively if you are using NgModules, you would add `provideClientHydration` to your root app module's provider list. ```typescript import {provideClientHydration} from '@angular/platform-browser'; import {NgModule} from '@angular/core'; @NgModule({ declarations: [RootCmp], exports: [RootCmp], bootstrap: [RootCmp], providers: [provideClientHydration()], }) export class AppModule {} ``` You can confirm hydration is enabled by opening Developer Tools in your browser and viewing the console. You should see a message that includes hydration-related stats, such as the number of components and nodes hydrated. Co-authored-by: jessicajaniuk <72768744+jessicajaniuk@users.noreply.github.com> Co-authored-by: alan-agius4 <17563226+alan-agius4@users.noreply.github.com> PR Close #49666 04 April 2023, 05:13:47 UTC
b2327f4 feat(core): Allow typeguards on QueryList.filter (#48042) To match the behaviour of Array.filter, typeguards can now be used on QueryList.filter to narrow the return type. Fixes #38446 BREAKING CHANGE: QueryList.filter now supports type guard functions, which will result in type narrowing. Previously if you used type guard functions, it resulted in no changes to the return type. Now the type would be narrowed, which might require updates to the application code that relied on the old behavior. PR Close #48042 04 April 2023, 02:35:35 UTC
6ca1a53 refactor(compiler-cli): workaround for CI failure in Windows (#49136) It seems that changes in prior commits led to a new error in the Windows CI job, likely due to its sandboxing setup in Bazel. This commit adds an explicit type annotation that should avoid the error. PR Close #49136 04 April 2023, 02:20:01 UTC
ff6608c refactor(compiler-cli): remove a flag that is always true in ngtsc (#49136) This flag was set to `true` by ngcc, but now that ngcc is gone this flag can be removed. PR Close #49136 04 April 2023, 02:20:01 UTC
2d6e6a1 refactor(compiler-cli): update comments to account for ngcc removal (#49136) This commit updates comments to account for the removal of ngcc. PR Close #49136 04 April 2023, 02:20:01 UTC
e5a30d9 refactor(compiler-cli): update compilation error message to not mention ngcc (#49136) No longer refer to an ngcc incompatibility now that ngcc has been removed. PR Close #49136 04 April 2023, 02:20:00 UTC
3f47535 refactor(compiler-cli): update `TraitCompiler` to account for ngcc deletion (#49136) There used to be a subclass of `TraitCompiler` in ngcc, but now that ngcc has been removed we can update `TraitCompiler` to no longer expose certain fields and methods. PR Close #49136 04 April 2023, 02:20:00 UTC
cfa9f31 refactor(compiler-cli): avoid clang-format inconsistency (#49136) There's an issue where formatting with `clang-format` doesn't agree with itself on how the docblock for a field named `import` should be indented; if it is indented then it removes the indentation, but then linting the source file reports an error where it wants to revert the indentation change. By using computed property syntax this bug is avoided. PR Close #49136 04 April 2023, 02:20:00 UTC
c20deb7 refactor(compiler-cli): only use a single type expression (#49136) The concept of "internal" and "adjacent" type expression used to be necessary to support ngcc, as it had to process downleveled class declarations using an IIFE, where the class name within the IIFE could be different from the outer class name. With the removal of ngcc we no longer need to make this distinction, so this commit removes these concepts entirely. PR Close #49136 04 April 2023, 02:20:00 UTC
9540f6d refactor(compiler-cli): remove unused dts declaration logic (#49136) This logic used to be in place to support ngcc, but with the removal of ngcc this is no longer relevant. PR Close #49136 04 April 2023, 02:20:00 UTC
d9060d9 refactor(compiler-cli): remove ngcc-only builtin functions (#49136) ngcc's reflection host would recognize tslib helpers and some JS builtin methods to allow the static interpreter to evaluate compiled and downleveled JS code, but now that ngcc has been removed this functionality is no longer being used. PR Close #49136 04 April 2023, 02:20:00 UTC
bbe4590 refactor(compiler-cli): remove support for ngcc-only declaration formats (#49136) This commit simplifies various parts of ngtsc to no longer support synthetic decorators, downleveled enum members and inline declarations. These concepts were present to support ngcc, but can be dropped now that ngcc has been removed. PR Close #49136 04 April 2023, 02:20:00 UTC
4b673d5 docs: Add error page for NG0504 error (#49689) This adds a detailed error page for the hydration invalid ngSkipHydration host error. PR Close #49689 04 April 2023, 02:19:27 UTC
9e9e131 docs: Add error page for NG0503 error (#49689) This adds a detailed error page for the hydration unsupported projection of DOM nodes error. PR Close #49689 04 April 2023, 02:19:26 UTC
f1566f3 docs: Add error pages for NG0501 and NG0502 errors (#49689) This adds a detailed error pages for the hydration missing siblings and hydration missing node errors. PR Close #49689 04 April 2023, 02:19:26 UTC
b7c5acb docs: Add error page for NG0500 hydration node mismatch error (#49689) This adds a detailed error page for the hydration node mismatch error. PR Close #49689 04 April 2023, 02:19:26 UTC
c912294 docs: fix typo (#49669) PR Close #49669 04 April 2023, 02:18:40 UTC
31f4efe docs: add hydration guide (#49665) This adds a guide for how to use hydration in Angular. PR Close #49665 04 April 2023, 02:17:58 UTC
719f6a0 refactor(core): remove unnecessary `reflect-metadata` import. (#49673) The import is not needed for the tests to run. PR Close #49673 04 April 2023, 02:17:02 UTC
ba3e9ea feat(devtools): Improve Set support in component properties. (#49316) With this commit, Sets are displayed with the label Set(#) where # is the size of the set. They are not expandable/editable though. Partial fix for #49312 PR Close #49316 04 April 2023, 02:15:34 UTC
aff1512 feat(http): allow `HttpClient` to cache requests (#49509) This commit adds a new option for `provideHttpClient` called `withHttpTransferCache()`. When this option is passed, requests done on the server are cached and reused during the bootstrapping of the application in the browser thus avoiding duplicate requests and reducing load time. This is the same as `TransferHttpCacheModule` in https://github.com/angular/universal/blob/main/modules/common/src/transfer_http.ts PR Close #49509 04 April 2023, 02:13:45 UTC
8019fed docs: fix typo in quick reference (#49655) Change indicatedr5t to indicated PR Close #49655 04 April 2023, 02:13:15 UTC
85ca1f9 build: update dependency concurrently to v8 (#49662) See associated pull request for more information. PR Close #49662 04 April 2023, 02:12:44 UTC
d11f5d7 build: update dependency google-closure-compiler to v20230228 (#49663) See associated pull request for more information. PR Close #49663 04 April 2023, 02:12:14 UTC
61bedaf refactor(core): handle a case when ngSkipHydration is applied to the root node of an application (#49675) This commit updates the logic to handle a case when the `ngSkipHydration` attribute is applied to the root node of an app. In this case, the hydration info should not be serialized and the contents of the app on the client should be cleared up before initial rendering. PR Close #49675 04 April 2023, 02:11:47 UTC
a5f1737 feat(core): expose onDestroy on ApplicationRef (#49677) This change exposes the onDestroy callback on the ApplicationRef as the public API. It is useful for cases where people need to execute cleanup logic on application teardown. Closes #49087 PR Close #49677 03 April 2023, 22:01:18 UTC
7870fb0 feat(platform-server): rename `provideServerSupport` to `provideServerRendering` (#49678) This commit renames `provideServerSupport` to `provideServerRendering`. PR Close #49678 03 April 2023, 22:00:13 UTC
de6dc5f release: cut the v16.0.0-next.6 release 03 April 2023, 20:37:20 UTC
b3d2e33 docs: fix typo (#49664) PR Close #49664 03 April 2023, 05:10:12 UTC
fa3909e fix(router): Ensure initial navigation clears current navigation when blocking (#49572) The navigation transition clears the current navigation in the finalize operator of the current navigation Observer. This commit both completes the `bootstrapDone` observable and updates the transition to only take 1 emit from the completed navigation. Either of these changes on their own would fix the issue. The latter is a preventative measure in case a mistake like the former is made again. fixes #49567 PR Close #49572 01 April 2023, 00:04:01 UTC
acff3c6 docs: fix typo in toh-pg6.md (#49141) Line 425. Change burning to burn. PR Close #49141 31 March 2023, 19:00:43 UTC
fda3f67 refactor(elements): `ComponentNgElementStrategyFactory` and `ComponentNgElementStrategy` are not part of the public API. (#49642) Per #37416, it has been chosen to not make them public. PR Close #49642 31 March 2023, 18:59:24 UTC
d7d6514 feat(core): Add ability to configure `NgZone` in `bootstrapApplication` (#49557) This commit adds a provider function that allows developers to configure the `NgZone` instance for the application. In the future, this provider will be used for applications to specifically opt-in to change detection powered by ZoneJS rather than it being provided by default. This API does _not_ specifically provide support for developers to define their own `NgZone` implementation or opt in to `NoopNgZone` directly. Both of these are possible today, but are effectively unsupported (applications that use these are left to their own devices to run change detection at the appropriate times). That said, developers can still use DI in `bootstrapApplication` to provide an `NgZone` implementation instead, it's just not specifically available in the `provideZoneChangeDetection` function. PR Close #49557 31 March 2023, 18:56:10 UTC
58c1faf refactor(core): update `bootstrapApplication` to get `NgZone` from providers (#49557) This commit updates the `bootstrapApplication` method to get the `NgZone` instance from DI. This will allow a future change to enable developers to configure `NgZone` in DI rather than adding the options to the top level like in `bootstrapModuleFactory` (which is done in order to get the NgZone instance without going through DI). PR Close #49557 31 March 2023, 18:56:09 UTC
01d4a13 build: update eslint dependencies to v5.57.0 (#49608) See associated pull request for more information. PR Close #49608 31 March 2023, 18:55:35 UTC
78a3298 refactor(router): Remove internal use of guard and resolve interfaces (#49548) These interfaces are deprecated and should not be used internally. PR Close #49548 31 March 2023, 18:51:50 UTC
12b2caa build: update scorecard action dependencies (#49609) See associated pull request for more information. PR Close #49609 31 March 2023, 18:49:46 UTC
6c1895f refactor(core): avoid incrementing a dev mode counter unnecessarily (#49656) This commit removes a code that increments the `rendererCreateComment` counter unnecessarily. The counter gets incemented even in hydration scenarios where we do not create a comment node. The counter still gets incemented in the right locations (when we *actually* create a node). PR Close #49656 31 March 2023, 18:49:13 UTC
de55fdf build: update cross-repo angular dependencies (#49649) See associated pull request for more information. PR Close #49649 31 March 2023, 18:46:15 UTC
1dc8480 refactor(router): Remove dead code (#49652) This warning is no longer produced because the legacy method of creating URL trees was removed in v16 PR Close #49652 30 March 2023, 23:12:06 UTC
81c9dd7 docs(router): Update common tasks guide to use input binding instead of ActivatedRoute (#49633) The easiest way to access route data is now to use direct bindings to component inputs rather than going through `ActivatedRoute`. The tour of heroes guide still uses `ActivatedRoute` for now. I was hesitant to remove all of the content in one swoop and the tour of heroes is quite a bit more involved. PR Close #49633 30 March 2023, 23:10:54 UTC
f982a3f feat(router): Opt-in for binding `Router` information to component inputs (#49633) Adds ability for `RouterOutlet` to bind `Router` information to the routed component's inputs. This commit also exposes some helpers for implementers of custom outlets to do their own input binding if desired. Resolves #18967 PR Close #49633 30 March 2023, 23:10:54 UTC
f19319e docs: update security guide to mention new CSP functionality (#49561) Updates the security guide to reflect the recently-added CSP APIs. PR Close #49561 30 March 2023, 23:10:06 UTC
e9dd7f0 refactor(core): Prevent reads and writes to signals at certain times (#49631) * Prevent reads of signals during the notification process. This shouldn't ever be triggered by user code but is more of a preventative for internal misuse. Reading a signal during notification would/could create glitches where the values being read are not updated to reflect the values being updated by the notification. * Prevent signal writes inside of computed's. These are meant to be derived values and should not have any side-effects like writing new values to other signals * Prevent signal writes inside of effects by default. Writing to signal values during the execution of an effect can lead to the `ExpressionChangedAfterItHasBeenCheckedError` if writing to signals that represent global state which is read in a parent component. This is mostly just a problem for `OnPush`/`CheckAlways` components, but with signals being new and pure signal components not even available yet, it will be the majority for a long time. PR Close #49631 30 March 2023, 23:09:12 UTC
07a1aa3 feat(forms): Improve typings form (async)Validators (#48679) With this commit, AsyncValidatorFn cannot be passed as ValidatorFn anymore in FormControl. fixes: #48676 PR Close #48679 30 March 2023, 18:47:29 UTC
39a648f refactor(core): Use (where applicable), `ViewContainer.createComponent` instead of relying on the `ComponentFactoryResolver`. (#49614) `ComponentFactoryResolver` has been deprecated for public usage since its not necessary anymore. Lets reflect that in the unit tests. PR Close #49614 30 March 2023, 18:43:35 UTC
9d96487 test(core): fix rxjs-interop tests which fail due to collision (#49651) The change in effect timing collided with the introduction of these rxjs-interop tests, resulting in them failing after the merge. This commit adjusts the tests to rely on the real effect timing. PR Close #49651 30 March 2023, 18:06:48 UTC
2703fd6 refactor: remove deprecated `EventManager` method `addGlobalEventListener` (#49645) This commit removed the deprecated `EventManager` method `addGlobalEventListener`. BREAKING CHANGE: Deprecated `EventManager` method `addGlobalEventListener` has been removed as it is not used by Ivy. PR Close #49645 30 March 2023, 16:47:54 UTC
e883198 feat(core): implement `takeUntilDestroyed` in rxjs-interop (#49154) This commit implements an RxJS operator `takeUntilDestroyed` which terminates an Observable when the current context (component, directive, etc) is destroyed. `takeUntilDestroyed` will inject the current `DestroyRef` if none is provided, or use one provided as an argument. PR Close #49154 30 March 2023, 16:44:38 UTC
8997bdc feat(core): prototype implementation of @angular/core/rxjs-interop (#49154) This commit adds the basic sketch for the implementation of `fromObservable` and `fromSignal`, the two basic primitives which form the RxJS interop layer with signals. PR Close #49154 30 March 2023, 16:44:38 UTC
8b7707d build(core): introduce `@angular/core/rxjs-interop` entrypoint (#49154) This commit adds the infrastructure for `@angular/core/rxjs-interop`, a new core entrypoint which provides bidirectional interoperability between Angular's built-in reactivity system of synchronous signals, and the RxJS `Observable` abstraction. The new entrypoint is set up as an empty shell in this commit, with its implementation to follow in a followup. PR Close #49154 30 March 2023, 16:44:38 UTC
267c5e8 refactor(core): remove DeepReadonly type wrapper for signals (#49154) We've been experimenting with the DeepReadonly type that would make signal values deeply read-only and prevent accidental changes without going to the owner of data. What we've found out during the experiments is that additional safety net has more drawbacks than benefits: it just introduces too much friction to be practical for daily usage. PR Close #49154 30 March 2023, 16:44:38 UTC
d786856 refactor(core): output hydration stats into a console in dev mode (#49617) This commit adds a logic to output basic hydration stats into a console. This is also helpful to ensure that hydration is enabled and works. PR Close #49617 30 March 2023, 16:42:05 UTC
91eac28 refactor(core): add a counter for components that skipped hydration (#49617) This commit adds a new metric into the `ngDevMode` to count a number of components that skipped hydration (where `ngSkipHydration` attribute was applied). PR Close #49617 30 March 2023, 16:42:05 UTC
50c58ce build: update domino digest to f29f047 (#49461) Update domino digest to f29f047 PR Close #49461 30 March 2023, 16:40:31 UTC
427b5fc test: update platform-server integration test expected CSS (#49461) This commit update the expected output due to changes in Domino. PR Close #49461 30 March 2023, 16:40:31 UTC
3dff638 build: update Domino to dc2f473e8155f0e21162e89681b5b0cb295d86e9 (#49461) Update own Domino SHA. Closes #44685 PR Close #49461 30 March 2023, 16:40:31 UTC
3379227 docs(core): fix view hierarchy links (#49629) fixes incorrect links to view-hierarchy (currently view-tree) Fixes #49623 PR Close #49629 30 March 2023, 16:39:39 UTC
1c3891c docs: fixed typo error (#49637) PR Close #49637 30 March 2023, 16:38:42 UTC
d596ec0 docs: Update Popup.service example to remove `ComponentFactoryResolver` (#49638) `ComponentFactoryResolver` has been deprecated and can be replaced by `createComponent()`. PR Close #49638 30 March 2023, 16:38:15 UTC
06e74a5 refactor(core): run effects during change detection (#49641) This commit updates the `effect` primitive and significantly changes the timing of effect execution. Previously, effects were scheduled via the microtask queue. This commit changes effects to run throughout the change detection process instead. Running effects this way avoids needing additional rounds of change detection to resolve effects, with the tradeoff that they're harder to use for model-to-model synchronization (which can be seen as a good thing). PR Close #49641 30 March 2023, 16:37:47 UTC
e254671 refactor(core): consolidate `LView` state from injectors (#49641) This commit consolidates the `RendererFactory` and `Sanitizer` properties of `LView` onto a single object, the `LViewEnvironment`. These properties are both set from DI when the root view is created, and not overridden when child views are created (but inherited from the parent view). This is a precursor commit to adding the `EffectManager` into the `LViewEnvironment`. PR Close #49641 30 March 2023, 16:37:47 UTC
f2ba192 release: cut the v16.0.0-next.5 release 29 March 2023, 22:41:24 UTC
cbe6807 refactor(core): Add default implementation for WeakRef (#49639) This commit adds a default implementation for WeakRef that uses strong references when the browser does not natively support WeakRef. PR Close #49639 29 March 2023, 22:33:27 UTC
3c7e637 fix(router): Route matching should only happen once when navigating (#49163) When navigating in the Router, the current approach does the redirects and the creation of the `RouterStateSnapshot` in two separate steps (applyRedirects and recognize). These two steps duplicate the route matching logic, resulting in user code on routes being executing twice (custom `UrlMatcher` and `canMatch` guards). This also duplicates the complex matching logic in two places, which increases the bundle size and maintenance burden. This commit combines the `applyRedirects` and `recognize` steps into a single matching algorithm. fixes #26081 PR Close #49163 29 March 2023, 21:40:41 UTC
2d25a2d docs: release notes for the v15.2.5 release 29 March 2023, 19:51:00 UTC
back to top