Daniel Kimmich

Your code is invalid, the for loop is missing a `track` expression, see the [docs](https://angular.dev/guide/templates/control-flow#track-for-calculating-difference-of-two-collections). Your code throws a build error: ``` ✘ [ERROR] NG5002: @for loop must have a...

This does not happen in a fresh Angular 12 project. What I did: - Create a new project using `npx @angular/cli@12 new` - Install ngx-translate using `npm i --save @ngx-translate/core@13`...

When the migration tool throws the "no component selected" error, you need to select the components that you want to migrate with the space bar.

Angular 17 dropped support for both the `@angular/material/theming` SCSS entrypoint and the legacy components. You need to remove all occurences from your code in order to be able to use...

Did you also consider splitting up your computation and writing logic? Something like the following: ```typescript class Test { value = input.required(); writableValue = signal(undefined); computedValue = computed(() => this.writableValue()...

For all TypeScript functions, this could work somewhat reliably by checking the `@developerPreview` JSDoc tags, assuming that Angular consistently sets this JSDoc tag on their features which are in developer...

Valid point, it's a bit confusing that the v17.3 docs app is already on M3 while all v17.3 projects have M2 by default.

With v5, the variables for foreground and background colors have been removed. There were major issues with it using the MDC-based components, especially filling the variables with the correct values....

Update: The token-based theming API didn't make it to Angular v17, so we need to wait a bit more. But apparently they are actively working on it.

What is the use case behind this? From my understanding, an application should have only one set of theme colors. I don't understand why a primary color should be different...