We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My suggestion meets these guidelines:
A keyword (private(set), maybe) to allow fields that are public for reading and private for writing.
private(set)
Workaround:
class MyClass { public readonly privateSetProp: number someMethod() { (this.privateSetProp as any) = 10 } }
The text was updated successfully, but these errors were encountered:
Duplicate of #37487. Used search terms: private public in:title. What search terms did you use?
private public in:title
Sorry, something went wrong.
I used private set. Closing
private set
No branches or pull requests
Suggestion
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
A keyword (
private(set)
, maybe) to allow fields that are public for reading and private for writing.Workaround:
The text was updated successfully, but these errors were encountered: