Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate eGRID and AVERT Location enums #69

Open
ryanhu021 opened this issue Feb 18, 2025 · 0 comments · May be fixed by #87
Open

Separate eGRID and AVERT Location enums #69

ryanhu021 opened this issue Feb 18, 2025 · 0 comments · May be fixed by #87
Assignees
Labels
backend Backend scope ready Ready for sprint

Comments

@ryanhu021
Copy link
Collaborator

ryanhu021 commented Feb 18, 2025

Description
We have a Location enum that is based on locations in the eGRID dataset. However, both the eGRID and AVERT schemas currently use this enum, and AVERT has a different set of locations. Refactor the schema so that we have separate EgridLocation and AvertLocation enums.

For eGRID, the locations should remain the same as the existing enum.

For AVERT, the locations should be US and all available regions in the data spreadsheet.

Acceptance Criteria
Separate enums, EgridLocation and AvertLocation, based on available locations in the respective dataset.

Steps:

  • In src/schema/egrid.ts, rename Location to EgridLocation. Update all references to match
  • In src/schema/avert.ts, create a new AvertLocation enum. Modify the AvertRecord schema to use this type
  • Update unit tests

Additional Information

@ryanhu021 ryanhu021 added ready Ready for sprint backend Backend scope labels Feb 19, 2025
@ishavarrier ishavarrier linked a pull request Feb 27, 2025 that will close this issue
6 tasks
@ishavarrier ishavarrier linked a pull request Feb 27, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend scope ready Ready for sprint
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants