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

chore!: do not allow 0 efficiency in input chart #565

Merged
merged 2 commits into from
Aug 9, 2024

Conversation

frodehk
Copy link
Contributor

@frodehk frodehk commented Aug 8, 2024

BREAKING CHANGE: 0 efficiency is not allowed in input charts.

ECALC-977

Have you remembered and considered?

  • I have remembered to update documentation
  • I have committed with BREAKING: in footer or ! in header, if breaking
  • I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
  • I have included the Jira issue ID somewhere in the commit body (ECALC-XXXX)

Why is this pull request needed?

Errors with 0 efficiency in input chart is catched late, and the error message does not point to the actual input file with the problem.

What does this pull request change?

Do not allow 0 efficiency in input file. It will give feedback much earlier, and points to the relevant file.

Issues related to this change:

https://equinor-ecalc.atlassian.net/browse/ECALC-977?atlOrigin=eyJpIjoiZDljMWJlYTczYzhjNGMwMTliM2FjNjU2YzVlNzJlNTAiLCJwIjoiaiJ9

@frodehk frodehk self-assigned this Aug 8, 2024
@frodehk frodehk requested a review from a team as a code owner August 8, 2024 10:20
@frodehk frodehk merged commit a38bb28 into main Aug 9, 2024
9 checks passed
@frodehk frodehk deleted the ECALC-977-improve-error-message-0-efficiency branch August 9, 2024 07:53
equinor-schen pushed a commit that referenced this pull request Aug 23, 2024
* chore: do not allow 0 efficiency in input chart

ECALC-977
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants