Skip to content

DEV: Complete moving the Economic Impact logic to Compound.py #4

Description

@JosephDYork

Since Economic impact is a compound endpoint, we need to ensure that it lives in the proper subclass. This will keep both developers and users from becoming confused about how the economic impact endpoint operates.

Activity

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

Metadata

Metadata

Assignees

Labels

Version 1.0 IssueTicket is blocking the version 1 release of EqLinkenhancementNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions