Skip to content

API_KEY Hardcoded #2

Description

@tbtalbottjr

The library hardcodes someones API_KEY. My understanding is that each client application should use their own API_KEY. This should be part of the authentication information used to initialize the library. A simple change would be to include an api_key argument to the setup method. You could default to the one in the code, but it seems like a bad idea to have one hard coded in the library.

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