feat(storage): rename StorageAnalyticsApi to StorageAnalyticsClient #1869
+22
−9
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.
Summary
Renames
StorageAnalyticsApitoStorageAnalyticsClientto align with the established naming convention where user-facing entry points use the "Client" suffix.Motivation
We have an architectural pattern where:
Client" = User-facing entry points (StorageClient,StorageVectorsClient)Api" = Internal building blocks/lower-level APIs (VectorBucketApi,VectorIndexApi,VectorDataApi)StorageAnalyticsApiwas incorrectly using the "Api" suffix even though it's a top-level user-facing entry point accessed viastorage.analytics. This inconsistency was confusing and didn't match the pattern used for vectors.Changes
StorageAnalyticsApi.ts→StorageAnalyticsClient.tsStorageAnalyticsApi→StorageAnalyticsClientStorageClient.tsandindex.tsImpact
@alpha(public alpha)StorageAnalyticsApitoStorageAnalyticsClientPattern Clarity
After this change, our naming is now consistent: