You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 separateEgridLocation
andAvertLocation
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
andAvertLocation
, based on available locations in the respective dataset.Steps:
src/schema/egrid.ts
, renameLocation
toEgridLocation
. Update all references to matchsrc/schema/avert.ts
, create a newAvertLocation
enum. Modify theAvertRecord
schema to use this typeAdditional Information
The text was updated successfully, but these errors were encountered: