Improve ContextProvider naming: rename get_table_provider --> get_table_source, deprecate get_table_provider
#7831
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
sql
alamb
reviewed
Oct 16, 2023
There was a problem hiding this comment.
Thank you very much @lewiszlw -- this is a very nice change and improves the readability in my opinion. The only thing I think we should do is avoid the breaking API change (by leaving in a deprecated warning, which I described in the commnets)
Otherwise, this looks great. Thank you 🙏
alamb
approved these changes
Oct 16, 2023
alamb
changed the title
ContextProvider naming: get_table_provider --> get_table_source, deprecate get_table_provider
alamb
changed the title
ContextProvider naming: get_table_provider --> get_table_source, deprecate get_table_providerContextProvider naming: rename get_table_provider --> get_table_source, deprecate get_table_provider
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Some field/method names are confused.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?