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
As a Carbon Aware Developer, I want the datasource handlers (EmissionHander, ForecastHandler) to directly call the datasource and remove the overhead of having Aggregators in between so that the code is cleaner and extensible.
This would prevent from creating a new Aggregator layer every time a new data source interface is created.
Acceptance Criteria
Ensure that the CA library consumes the Datasources directly.
Remove reference to the Aggregator project
Mark Aggregator methods with 'deprecated' flag
Unit Tests are completed, and the code passes tests
Update Documentation, including Architecture diagrams, if needed
Dependencies
Task List
List of tasks (punch list) needed to complete the user story
Sprint-Ready Checklist
Acceptance criteria defined
Acceptance criteria are verifiable/testable
External / 3rd Party dependencies identified
Engineering team understands acceptance criteria
Is the user story small enough to be implemented in a short amount of time, but large enough to provide value?
The text was updated successfully, but these errors were encountered:
Description
As a Carbon Aware Developer, I want the datasource handlers (EmissionHander, ForecastHandler) to directly call the datasource and remove the overhead of having Aggregators in between so that the code is cleaner and extensible.
This would prevent from creating a new Aggregator layer every time a new data source interface is created.
Acceptance Criteria
Dependencies
Task List
Sprint-Ready Checklist
The text was updated successfully, but these errors were encountered: