Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Check if everything is @internal or private that should be #1119

Open
JakeQZ opened this issue Nov 25, 2021 · 0 comments
Open

Check if everything is @internal or private that should be #1119

JakeQZ opened this issue Nov 25, 2021 · 0 comments
Labels
cleanup

Comments

@JakeQZ
Copy link
Contributor

JakeQZ commented Nov 25, 2021

We don't want to be exposed to having to support accidental API leaks (e.g. a class not marked @internal that was only intented for internal use, or a method not declared private that was not intended for use by external or extending classes).

Needs a fine-toothed comb to check this.

(Added following discussion at #1118.)
@JakeQZ JakeQZ added the cleanup label Nov 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JakeQZ