-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
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
Underscore internal methods that are public #2100
base: main
Are you sure you want to change the base?
Conversation
We have plenty of internal methods that are not meant to be used externally, often tagged @Private. In a recent office hours, @camertron, @BlakeWilliams and I noted that we should better indicate when an internal method should not be dependended on. I've done so here by adding a `__vc_` prefix as is convention in other parts of the codebase already. As a separate exercise, we should probably re-evaluate our public API surface area and see if we can make any public methods private.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok to me, but should we target this change for v4.0 since we're technically changing the public API?
40a40a3
to
ccb9505
Compare
@camertron I'm torn. These APIs are not documented publicly, so I'm leaning towards this not being a breaking change. |
Yeah I hear you... I worry that we're going against semver by doing this though. Even though the methods in question aren't documented, they're still public, and semver is pretty clear about needing a major bump for API changes. |
I could totally see someone using I think hiding the compiler like this makes a ton of sense though. I'd opt for v4, personally. |
We have plenty of internal methods that are not meant to be used externally, often tagged @Private. In a recent office hours, @camertron, @BlakeWilliams and I noted that we should better indicate when an internal method should not be dependended on. I've done so here by adding a
__vc_
prefix as is convention in other parts of the codebase already.As a separate exercise, we should probably re-evaluate our public API surface area and see if we can make any public methods private.