-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Final review of internal code usage #15695
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
providers-beware
type-enhancement
Milestone
Comments
This was referenced May 12, 2019
ajcvickers
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Jul 23, 2019
ajcvickers
added a commit
that referenced
this issue
Jul 23, 2019
Mostly moving types to different namespaces (internal or public), and a few renames. Also, checked where Cosmos and other providers were using internal types and made those pubic. Re-enabled API consistency, except for NotNull attributes (since these aren't breaking to add later.) Fixes #12084 Fixes #15107 Fixes #15695 Fixes #15796
ajcvickers
added a commit
that referenced
this issue
Jul 23, 2019
Mostly moving types to different namespaces (internal or public), and a few renames. Also, checked where Cosmos and other providers were using internal types and made those pubic. Re-enabled API consistency, except for NotNull attributes (since these aren't breaking to add later.) Fixes #12084 Fixes #15107 Fixes #15695 Fixes #15796
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
providers-beware
type-enhancement
Once query is ready, we need to do a final review of internal code used by providers. Everything other than query and conventions should be in a good state, but we may as well check everything one last time when doing the work for query.
The text was updated successfully, but these errors were encountered: