You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some properties (including functions) on Command which are intended to be private but do not start with an underscore.
Advantages of renaming them are:
make it clearer that they are private
reduce noise in code completion suggestions in editors
reduce name collisions when storing option values as properties on Command
We would treat this as a breaking change and a major version bump, since some clients will be using private properties whether by accident or design.
I am interested if many readers are using or overriding private properties. I suspect some clients customise the error display via missingMandatoryOptionValue et al.
For interest, there is a proposal for true private fields in javascript:
I like the idea of cleaning up the autocompletion, but no one has complained. Since it would break anyone currently using a private property, not confident the cost/benefit is worthwhile for now.
We have some properties (including functions) on Command which are intended to be private but do not start with an underscore.
Advantages of renaming them are:
We would treat this as a breaking change and a major version bump, since some clients will be using private properties whether by accident or design.
I am interested if many readers are using or overriding private properties. I suspect some clients customise the error display via
missingMandatoryOptionValue
et al.For interest, there is a proposal for true private fields in javascript:
The text was updated successfully, but these errors were encountered: