-
Notifications
You must be signed in to change notification settings - Fork 46
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: refacto useOutputData #9642
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 #9642 +/- ##
==========================================
- Coverage 38.22% 38.19% -0.04%
==========================================
Files 995 995
Lines 91893 91917 +24
Branches 1189 1193 +4
==========================================
- Hits 35127 35104 -23
- Misses 56312 56358 +46
- Partials 454 455 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ac3a4af
to
e989762
Compare
9dfbfc1
to
28d2249
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.
Very nice PR! useOutputTableData was a mess, it's a lot more straightforward now
Edit : nevermind, I think the line I chose for testing is just bugged, but it seems to work fine for other lines, and possibly that issue has nothing to do with the pr. I'm checking ^^
Edit edit : yep the bug (waypoints in the wrong order with the wrong informations for paris gare de lyon when going from gare de lyon to lyon) is there on dev also. Sorry!
front/src/applications/operationalStudies/views/SimulationResults.tsx
Outdated
Show resolved
Hide resolved
front/src/modules/timesStops/helpers/__tests__/arrivalTime.spec.ts
Outdated
Show resolved
Hide resolved
28d2249
to
79322d9
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.
Thank you for this great refacto, it's really easier to handle this hook now :)
Left some comments, feel free to contact me. to discuss some of them
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.
56912ce
to
30ff814
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.
Lgtm and tested, great job !
df49ba8
to
01dfea7
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.
Tested and LGTM, great work!
The logic to compute the data for the output table has been modified: - instead of handling both pathsteps and regular operational points on the path at the same time, we now handle first the path steps (which may have some additional information, such as margins, schedules, stop duration...) and then handle the regular operational points (we only need to compute the arrival time). This simplifies a lot the hook - instead of re-computing the time of each waypoint, we now use the times received in the summary of the train. Signed-off-by: Clara Ni <[email protected]>
36ce995
to
6593638
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.
LGTM for e2e tests
closes #8949
will also close #8848