Closed andreElrico closed 2 years ago
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
Duplicate of #6264.
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.
Feature Description
14113
I would like to know your stand on making all private into protected members?
The cdk is meant to act as "building blocks" right? So it would be nice to extend those building blocks and change current members.
Im fine with protected members not being "protected " :D from breaking changes. At least I can start working without ==>
this['_somePrivateMember']
etc ...Use Case
Always when you want to build cool stuff by extending CDK. To bad there is no material-drag-drop ... esp. drag-drop is completly shut down :-(
Current workarounds
this['_somePrivateMember']
madness.