-
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: magic wand revamp #6210
Conversation
2030abe
to
57d840b
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## dev #6210 +/- ##
============================================
- Coverage 27.30% 26.93% -0.37%
Complexity 2136 2136
============================================
Files 952 961 +9
Lines 124900 124258 -642
Branches 2690 2574 -116
============================================
- Hits 34106 33472 -634
- Misses 89189 89297 +108
+ Partials 1605 1489 -116
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
You could move auto_fixes.rs
into auto_fxes/
and rename it to mod.rs
.
Otherwise, LGTM.
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 (tested locally). I agree on mv auto_fixes.rs autofixes/mod.rs
.
35ff70d
to
583b3f9
Compare
583b3f9
to
d4d0b51
Compare
If we want to keep opportunities to parallelize this code, all the errors related to the same object should be addressed together. It will become important when some `Operation::Update` will happen and need to be ordered correctly.
8d0cf43
to
24faeea
Compare
Tests are going in another PR (to avoid blocking other work). |
If we want to keep opportunities to parallelize this code, all the errors related to the same object should be addressed together. It will become important when some
Operation::Update
will happen and need to be ordered correctly.Still missing some tests on (can take inspiration on
fn fix_track_section()
):fn fix_catenary()
fn fix_detector()
fn fix_operational_point()
fn fix_route()
fn fix_signal()
fn fix_speed_section()
fn fix_switch()