You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently customization of components is done through templates added as content children. This may lead to a lot of duplicate code in templates. As primeng already uses @angular/cdk and has it as a dependency it may be useful to allow passing portals into components. These could easily be reused.
For example icons could be easily created through a factory including an already existing icon component and massing the icon as data to the portal.
So for example considering the pick list code could look like this
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently customization of components is done through templates added as content children. This may lead to a lot of duplicate code in templates. As primeng already uses
@angular/cdk
and has it as a dependency it may be useful to allow passing portals into components. These could easily be reused.For example icons could be easily created through a factory including an already existing icon component and massing the icon as data to the portal.
So for example considering the pick list code could look like this
Beta Was this translation helpful? Give feedback.
All reactions