Skip to content

Create enumerations and constants for important fields rather than using literal strings #302

Description

@christophertubbs

There are several spots in the code base where important words are used, such as "feature_id", "reference_time", URLs, USGS parameter codes, common request query parameters, etc. These need to be placed in a common location and referenced in order to maintain correctness and common spelling. If package A downloads data and stores important data in "fieldName" and package B has a function that relies on "fieldName", the utilization of magic strings will eventually cause issues due to a mismatch of terminology, versions, or spelling.

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

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions