-
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: LMR: fix length, mass and speed reset #10447
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 #10447 +/- ##
==========================================
- Coverage 81.93% 81.91% -0.03%
==========================================
Files 1078 1081 +3
Lines 107555 107790 +235
Branches 733 734 +1
==========================================
+ Hits 88125 88293 +168
- Misses 19391 19458 +67
Partials 39 39
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
854df7b
to
1522505
Compare
@Akctarus When i select Traction engine using the combobox above i have these messages on each filled input is it the intended behaviour ? and have to close them manually which is more of a ui-core improvement |
yes it is, the user must be informed visually as soon as the app changes a piece of data he had previously changed. To close them, yes maybe we should improve that, but in any case the messages close by themselves, if we change traction engine |
78cd147
to
8e73583
Compare
front/src/applications/stdcm/components/StdcmForm/StdcmConsist.tsx
Outdated
Show resolved
Hide resolved
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.
If I change the speed limit tag, the length and mass fields are updated when there should be only the vmax one who changes
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.
fixed by : 6c4c0d8
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.
Some of the changes you made here broke some things :
Enregistrement.de.l.ecran.2025-01-31.a.09.01.43.mov
Sometimes when I just change the mass after switching a rs, the tooltip pops. Same if I change the speed limit tag.
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.
Normal behavior :
- I select a BB 15 000 > the vmax goes to 160
- I put a ME 120 speed limit tag > the vmax goes to 120
- I switch to BB 64700 > the vmax goes to 80 (even with ME 120 as expected) > no message as expected
Same test with one change :
- I select a BB 15 000 > the vmax goes to 160
- I manually change the vmax to 150
- I put a ME 120 speed limit tag > the vmax goes to 120
- I switch to BB 64700 > the vmax goes to 80 (even with ME 120 as expected) > there is a info tooltip
I don't think we should have one as the vmax I manually entered has already been overridden by the change of the speed limit tag. Maybe when we pass inonSpeedLimitByTagChange
, we shouldsetMaxSpeedChanged(false);
? (didn't test)
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.
fixed :)
30f3388
to
75eecee
Compare
front/src/applications/stdcm/components/StdcmForm/StdcmConsist.tsx
Outdated
Show resolved
Hide resolved
front/src/applications/stdcm/components/StdcmForm/StdcmConsist.tsx
Outdated
Show resolved
Hide resolved
575c36e
to
0901f41
Compare
Signed-off-by: Theo Macron <[email protected]>
0901f41
to
9d86d3c
Compare
CONSIST_TOTAL_MASS_MAX, | ||
} from '../utils/consistValidation'; | ||
|
||
const useConsistFieldStatus = ( |
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 think it's better to have different names for useConsistFieldStatus
and useStatusWithMessage
, was the naming of the two hooks with the same name intentional ?!
Can you rebase your branch please, for easier testing :) |
closes #10106 and fix #10270
should respect the expectations of this: https://github.com/osrd-project/osrd-confidential/issues/903