Skip to content

drop as_ prefix from as_X_client from storage crates #847

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

Merged
merged 1 commit into from
Jun 24, 2022

Conversation

bmc-msft
Copy link
Contributor

Per discussion in #676, this renames the various as_X_client to X_client

Per discussion in Azure#676, this renames the various as_X_client to X_client
@bmc-msft bmc-msft requested a review from rylev June 23, 2022 15:14
Copy link
Contributor

@rylev rylev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is definitely better so we should merge it. We might need to rethink the client hierarchy within the storage crates though...

storage_account
.as_table_service_client()
.table_service_client()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this just be table_client? What's the benefit of the service nomenclature?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One of the things that could stand clearing up is this issue. I understand the underlying intent in this implementation, but it's confusing. Currently, with a StorageAccount.table_service_client gets you a TableServiceClient.

TableServiceClient lets you:

  1. list tables
  2. get a TableClient for a specified table.

TableClient lets you interact with a given table (create it, query it, delete it, insert things into it, etc)

@bmc-msft bmc-msft merged commit 94ab068 into Azure:main Jun 24, 2022
@bmc-msft bmc-msft deleted the rename-storage-client-methods branch June 24, 2022 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants