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.
refactor(ngContent): rename <ng-content> to <ng-slot>
See original GitHub issueTurns out that the Shadow DOM’s spec <content> element has been deprecated and is now called <slot>.
Do we want to align <ng-content> accordingly?
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Changing the name of a component in Angular 12 [duplicate]
1 Answer 1 · Rename the paths to templateUrl and styleUrls under the @Component Type Decorator in <new-name>.component.ts . · Rename the Class ......
Read more >Learn Angular Multi Slot Content Projection - YouTube
In this video we are going to do a demo of how Angular Multi- slot content projection works, using ng - content and...
Read more >Ng content in Angular 12 tutorial - Content Projection - YouTube
Ng content in Angular 12 tutorial - Content Projection. We explore the concept of Content ... The topics covered include Single slot conte......
Read more >Inverting the control to make super reusable components!
We do that with one of my favourite Angular features, <ng-content> . Each slot is analogous to an argument for the “constructor” of...
Read more >Refactoring Angular Apps to Component Style - Tero Parviainen
Remove the part of the copied content that you want to leave in the original location. Replace it with an ng-transclude .
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 Free
Top 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
We should stick with
content. We have content injection, content change detection, contentBindings, etc. In all of those cases slot does not make sense.We may implement the new functionality, but that is outside the scope of this issue.
Closing.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.