-
Notifications
You must be signed in to change notification settings - Fork 45
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
editoast: refacto path item location to add track and label information #9800
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 #9800 +/- ##
==========================================
+ Coverage 37.82% 38.19% +0.37%
==========================================
Files 994 998 +4
Lines 91126 92204 +1078
Branches 1176 1192 +16
==========================================
+ Hits 34466 35220 +754
- Misses 56206 56528 +322
- Partials 454 456 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9ba7f2c
to
239687f
Compare
a4ea449
to
41128bd
Compare
41128bd
to
d0ed7ef
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.
I'm missing a bit of context to understand exactly what is going on on the second commit. More generally, it would be nice to fill up the description of the PR?
Apart from that, thanks for the work, nice and easy to review. I have however a comment questionning the implementation. Leaving a "Request changes" until we know more.
47e283c
to
78a0f76
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.
Thanks for the modification of the implementation with TrackReference
. I've made a few more comments, but nothing blocking now 🎉
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.
Great PR, not tested yet.
editoast/src/generated_data/sql/generate_operational_point_layer.sql
Outdated
Show resolved
Hide resolved
editoast/migrations/2024-11-25-111024_add_track_field_operational_point_layer/up.sql
Outdated
Show resolved
Hide resolved
78a0f76
to
8078784
Compare
2a7585f
to
db6a27d
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.
- We should at least add one test with a track reference.
- Nitpick: We are using
track_name
in the infra format. Why usingtrack_label
for the train schedule?
Here is a train_schedules.json I used to test it.
d70428f
to
ea32b24
Compare
Signed-off-by: Youness CHRIFI ALAOUI <youness.chrifi@gmail.com>
ea32b24
to
f5fcbf9
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
2168f09
to
43810c4
Compare
Signed-off-by: Youness CHRIFI ALAOUI <youness.chrifi@gmail.com>
43810c4
to
e126d29
Compare
No description provided.