-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
deprecate(bigquery): deprecate client.dataset()
in favor of DatasetReference
#7753
Conversation
@crwilcox I was inspired by our conversation today. Note: I've created this as a draft pull request because after I made this commit, I realized we still call |
@tswast Gentle ping to see if there are any updates on this PR. |
@busunkim96 I've worked with @sduskis to allocate some contractor resources for the necessary code sample updates before we unleash this PR. Is it an issue if we keep this open for now? |
@tswast Nope, I just wanted to check. 😸 Thanks! |
074af14
to
5a1bab8
Compare
…Reference Now that all client methods that take a `DatasetReference` or `TableReference` also take a string, the `client.dataset()` method is unnecessary and confusing.
5a1bab8
to
cec97ff
Compare
client.dataset()
deprecation.client.dataset()
in favor of DatasetReference
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.
There are still a lot of client.dataset()
calls in snippets.py
, but that file is deprecated, IIRC.
The rest looks good, aside from a remark on a possible grammar thingy.
This method is deprecated. Construct a | ||
:class:`~google.cloud.bigquery.dataset.DatasetReference` using its | ||
constructor or use a string where previously a reference object was | ||
used. |
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.
Would it make sense to use the standard Sphinx directive for deprecations?
The text itself is already clear, though.
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.
The Might still be worth investigating, though. Edit: Also happens on Update: #10195 fixes it. |
Co-Authored-By: Peter Lamut <plamut@users.noreply.github.com>
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 good now. 👍
Now that all client methods that take a
DatasetReference
orTableReference
also take a string, theclient.dataset()
method isunnecessary and confusing.
Closes #8989.