Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Protected fields #11

Closed
kobezzza opened this issue May 19, 2015 · 3 comments
Closed

Protected fields #11

kobezzza opened this issue May 19, 2015 · 3 comments

Comments

@kobezzza
Copy link

What about protected fields, ie fields and methods can be used within a class and his children, but can't be used from the outside?

@zenparsing
Copy link
Member

Protected fields might be a future extension.

Personally, I don't care to ever see protected access.

@indolering
Copy link

Protected fields might be a future extension.

I'm worried that not addressing the protected API will lead to a less coherent syntax.

Personally, I don't care to ever see protected access.

Really? I'm working on a plugin system right now and I find myself grasping for a protected API. Any essential readings on the topic?

@littledan
Copy link
Member

See https://github.com/tc39/proposal-private-fields/blob/master/DECORATORS.md for discussion of how this proposal can extend to protected fields through use of decorators

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants