Angular wrappers duplicate component inputs and outputs
In the cited Angular reports, developers wrapping components had to redeclare each input and output, including adding EventEmitter plumbing, and dynamic components were difficult to configure and listen to. That creates repetitive glue and makes forwarding easy to forget. The reports date from 2017, so the current size of the problem needs validation against newer Angular APIs.
For angular developers building wrapper and dynamic components. Mentioned from Mar 2017 to Sep 2020 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I cannot figure out another way to do the same thing without write all the Input on the wrapper again. When dealing with Output, it's even verbose because you have to introduce EventEmitter for each Output again
There is no way to set @Inputs or subscribe to @Output events of the Component created by NgComponentOutlet
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks