The Angular team has introduced a new migration to help developers update their decorator-based inputs to the new signal API. Signal inputs provide updates to the input functionality while maintaining feature parity with decorator-based inputs. One of the primary reasons to update is type-safety, which enables developers to remove brittle code patterns. Signal inputs also make input monitoring simpler. The new API can be used to refactor code that uses the ngOnChanges lifecycle hook to track updates to inputs. The migration can be run via the Angular CLI or as code refactoring actions in VSCode. The tooling will update the @Input declarations and adjust references to inputs, introducing variables where necessary. The migration is configurable and features options to help choose the right strategy to migrate code. The Angular team is excited to continue moving forward and realizing their vision for a new reactivity model. The new signal API is expected to simplify the mental model of Angular developers and make it easier to reason about state synchronization and flow.