Create tooling to make Angular wrapper for easy consumption in target projects and to ensure existing tests (badge.component.spec.ts) can be run.
Stencil maintainers have some considerations on why Angular wrappers makes sense here.
If we want to ensure backward compatability, there are three key arguments for creating the wrappers:
If there are no angular wrappers, consumers have to use CUSTOM_ELEMENTS_SCHEMA in all modules, effectively ignoring tag validation.
View queries like ViewChild(SomeComponent) will no longer work, and will have to be re-written with the element name instead.
No dependency injection of components possible if there is no angular type
Issues
[x] Single hand coded wrapper with inputs, outputs and slotted content, for badge
[x] #3496
[ ] #3498
[ ] Extend hand coded wrapper with control value accessor functionality
Create tooling to make Angular wrapper for easy consumption in target projects and to ensure existing tests (
badge.component.spec.ts) can be run.Stencil maintainers have some considerations on why Angular wrappers makes sense here. If we want to ensure backward compatability, there are three key arguments for creating the wrappers:
ViewChild(SomeComponent)will no longer work, and will have to be re-written with the element name instead.Issues
Further reading