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.
Make component methods protected to support Component inheritance
See original GitHub issueType of issue: (check with “[x]”)
- [X] New feature request
- [ ] Bug
- [ ] Support request
New feature request:
In version 2.3 Angular added component inheritance. I wondered whether it would be possible to the component methods protected (instead of private) where suitable, allowing us to extend the components to more easily customise behaviour.
For example, the UploadButtonComponent does much of what I need it do, but I would like to slightly change the logic around when to upload the file. With the current implementation, I would have to create my own button component and use the UploadService from scratch, and repeat much of the code already found within UploadButtonComponent. If functions such as uploadFiles were protected instead of private, I wouldn’t need to do this.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@JonnyHeavey I think is a good idea. In this way, we can take advantage of the new inheritance introduced in the Angular version 2.3. I think we will prioritize this refactoring and modify the visibility.
Depends on #1522