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

document and test forecast proposal validation rules #181

Open
catkins-miso opened this issue Oct 9, 2024 · 0 comments
Open

document and test forecast proposal validation rules #181

catkins-miso opened this issue Oct 9, 2024 · 0 comments
Assignees
Labels
Task catch-all for tasks not associated with spec changes

Comments

@catkins-miso
Copy link
Contributor

see #124

Also:
This is not yet part of the specification yet, per se, but a missing period for any resource in a proposal should result in the proposal for that particular resource being rejected as invalid. https://trolie.energy/example-narratives/submitting-forecasts.html#invalid-forecasts-for-individual-resources-should-be-tolerated

Similarly, a limits snapshot missing a period for any resource in the snapshot is a server error.

@catkins-miso catkins-miso added the Task catch-all for tasks not associated with spec changes label Oct 9, 2024
@catkins-miso catkins-miso added this to the Conformance Suite milestone Oct 9, 2024
@catkins-miso catkins-miso self-assigned this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task catch-all for tasks not associated with spec changes
Projects
None yet
Development

No branches or pull requests

1 participant