-
Notifications
You must be signed in to change notification settings - Fork 44
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
front: enable power restrictions merge #10561
base: dev
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #10561 +/- ##
==========================================
- Coverage 81.91% 81.89% -0.02%
==========================================
Files 1079 1079
Lines 107233 107331 +98
Branches 729 729
==========================================
+ Hits 87840 87901 +61
- Misses 19353 19390 +37
Partials 40 40
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
cecdc25
to
a487ade
Compare
…ot be retrived Signed-off-by: Clara Ni <[email protected]>
… restrction range When editing the first power restriction range, an extra empty range was added (range from 0 to 0). This was a bug and should not occur anymore. Signed-off-by: Clara Ni <[email protected]>
…alid Signed-off-by: Clara Ni <[email protected]>
Signed-off-by: Clara Ni <[email protected]>
a487ade
to
5e2dc72
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(was just passing by, didn't review all the code)
); | ||
|
||
let newPowerRestrictionRanges: PowerRestriction[] = []; | ||
let newPathSteps: PathStep[] = [...state.pathSteps].map((step) => step!); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit : we can probably add an early check and throw
if a path step is null because we don't have access to the power restriction tool if origin or destination are null (meaning there is no pathfinding)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interval.editor.mov
It seems if you cut the ranges multiple times and merge two of them, you're not able to merge the ranges with a position lower than the first cut.
It does work for the range positioned after, and also for ranges two steps below the first cut.
EDIT: tried again, and was able to merge ranges before the first cut (at least 2 steps before the first cut), except for the range that is right before the first cut.
closes #8850