Skip to content

Review public APIs (make sure they are "Pythonic") #101

@toddbaert

Description

@toddbaert

We know some of the internals of the SDK are a bit "Java-y"; these can be refactored later. However, before a 1.0 we need to make sure the public APIs are idiomatic to ensure we don't regret or design choices post-1.0.

Definition of done:

  • Review SDK, issues created for public API changes if necessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions