Skip to content

HarborAsyncClient is too verbose of a name #64

Description

@pederhan

The name HarborAsyncClient is technically correct, but is incredibly verbose. As this package is async-first, having Async in the class name seems superfluous. While we can't get rid of this name entirely because of backwards-compatibility, we can introduce a new alias that can be imported instead.

Some suggestions:

  • Harbor
  • HarborAPI
  • HarborClient
    • In this case we need to break backwards-compatibility with imports of harbor.HarborClient, which currently is a shorthand for harbor.client_sync.HarborClient, and then rename the existing one to harbor.client_sync.HarborSyncClient.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions