Make component methods protected to support Component inheritanceSee original GitHub issue
Type 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.
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
@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.