Make sure that `*RootFormComponent` uses the `@DataInput` decorator
See original GitHub issueI spent 15mn debugging an AutomaticRootFormComponent
trying to understand why the values where not passed from the parent down to the component on init (and never actually…).
Turns out it’s Friday and I forgot to use DataInput
🤦♂️
I think it might be worth adding a runtime check to make sure we’re using it on the *RootFormComponent
s.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Passing data into Angular components with @Input
This decorator tells Angular to treat count as an input binding, and if a piece of data is supplied, the count is then...
Read more >Angular 14 @Input Decorator Tutorial with Example
In this topic I will be teaching you how you can send data from parent component to child component using @Input Angular decorator....
Read more >Angular2 RC5: Can't bind to 'Property X' since it isn't a known ...
If 'create-report-card-form' is an Angular component and it has 'currentReportCardCount' input, then verify that it is part of this module.
Read more >Working with Angular 4 Forms: Nesting and Input Validation
Forms in Angular applications can aggregate the state of all inputs that are under that form and provide an overall state like the...
Read more >NgModules - Angular
It identifies the module's own components, directives, and pipes, making some of them public, through the exports property, so that external components can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Checking for this surely helps, but I feel the best option is to add schematics to the package and ask people to please use those. This would also make sure one can never again forget to add the component providers (another one of those things that is easily forgotten).
🎉 This issue has been resolved in version 5.2.0 🎉
The release is available on:
Your semantic-release bot 📦🚀