Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

POC: investigate pros/cons of switching from `ng-content` to `slot`

See original GitHub issue

Is this a bug, enhancement, or feature request?

feature request

Briefly describe your proposal.

Currently, when you have nested Angular custom elements, and the child element contains ng-content or content elements in its template, content projection/insertion points don’t work. It works if it is used slot elements. More information can be found here: angular/angular/issues/24536

The idea is to explore the option of migrating from using ng-content to slot.

Which versions of Angular and Fundamental NGX are affected? (If this is a feature request, use current version.)

angular 7.2 fundamental-ngx - latest

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

fkolarcommented, Oct 26, 2019

as you already know you can use both in angular to project the content and I think the only added value as of now if you plan to use your angular component as custom elements. In such case your component is ready for it.

When we implemented a fiori3 shellbar as customer element so it can be used in both angularJS apps and as well as in angular we had to use slots inside angualr components there was no other way - but in here I am not sure…

0reactions

droshevcommented, Nov 6, 2021

@fkolar do you know how many components would be affected? And what should we use to replace them?