Find PrimeNG members that became signals

MSAL

Marks the TypeScript that reads or sets a member of a PrimeNG component or directive which a major turned from a property into a signal, such as table.selection of a Table in PrimeNG 22, which is read as table.selection() from then on and can no longer be assigned, and lists it in the PrimeNgMigrationWork data table. It knows the component by the type a variable, field or parameter is declared with, or by the viewChild query that holds it, since the types of the project are still those of the PrimeNG it had.

org.openrewrite.javascript.migrate.primeng.FindPrimeNgSignalMembers

Required

The PrimeNG major version to upgrade to, from 19 to 22. The recipe applies the changes of every major after the one the project declares, up to this one.

Optional

Change the code of a project only once its primeng dependency is at the target version, having been below it when the run began. The UpgradeToPrimeNG recipes set this, so that a project whose dependency upgrade the package manager refuses keeps the code written for the version it stays on. The changes then come in the recipe cycle after the one that upgrades the dependency, which the recipe listing both has to ask for.

Apply only the changes the target major made, not those of the majors before it. The UpgradeToPrimeNG recipes set this, since each of them composes the upgrade to the major before.

mod run . --recipe=org.openrewrite.javascript.migrate.primeng.FindPrimeNgSignalMembers \ -P targetVersion=22

Install it once, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.