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.

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

what if... for 2.0.0 we made (almost) everything internal #820

Closed
TylerLeonhardt opened this issue Dec 14, 2018 · 0 comments · Fixed by #1183
Closed

what if... for 2.0.0 we made (almost) everything internal #820

TylerLeonhardt opened this issue Dec 14, 2018 · 0 comments · Fixed by #1183
Labels

Comments

@TylerLeonhardt
Copy link
Member

There's only a handful of things that really should be public and since we haven't published a nuget package in ages, it's not like anyone is depending on us like that at the moment (except maybe @SeeminglyScience 😄)

Who do you think we'd break if we made everything that's public to internal?

We'd keep stuff like $psEditor and such public... but everything else could be made internal. That way 2.0.0 onward we can go from internal to public where it makes sense.

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

Successfully merging a pull request may close this issue.

2 participants