Overview of the feature

Angular 17.1 introduced the new Input Signal API which uses the input() or input.required() function to expose inputs to the component as an InputSignal instead of a plain value. Currently, these are shown in the documentation as properties and not as inputs, which differs from how inputs accessed using @Input() are represented in the documentation.

Motivation for or Use Case

InputSignals are a comfortable way to get your inputs as a signal and will see widespread adoption in the near future. We are using compodoc in our company to generate documentation, not only as a standalone documentation but also for storybook. Since InputSignals are currently not correctly represented in the documentation (which a lot of users rely on), this prevents us from switching to the new API.

Related issues

Not that I am aware of.