front: fix track selection after timestops changes

[RomainValls]

Closes #10532

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.93%. Comparing base (eeb8aa2) to head (5c43382).
Report is 68 commits behind head on dev.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev   #10624      +/-   ##
==========================================
- Coverage   81.93%   81.93%   -0.01%     
==========================================
  Files        1078     1078              
  Lines      107555   107560       +5     
  Branches      733      733              
==========================================
+ Hits        88125    88126       +1     
- Misses      19391    19395       +4     
  Partials       39       39              

Flag	Coverage Δ
editoast	74.38% <ø> (-0.02%)	⬇️
front	89.42% <100.00%> (+<0.01%)	⬆️
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.50% <ø> (ø)
tests	88.14% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[achrafmohye]

@RomainValls when i add a stop time i still have v2 and not V1BIS that i made as the track for the train stop in Macon, is it the case or am i missing something ?

[RomainValls]

@RomainValls when i add a stop time i still have v2 and not V1BIS that i made as the track for the train stop in Macon, is it the case or am i missing something ?

I tried again, and it seems fixed for me :

Enregistrement.de.l.ecran.2025-02-06.a.18.07.40.mov

I also tried other tracks, and by editing the timestop after I added the train first, and edited it after.
@Math-R what about you ?

[achrafmohye]

Thanks for the fix, it's good for me now, i think you can add a todo if the fix regarding the types proposed by @Synar to be done by someone else in a seperate PR

[Math-R]

Looks good to me ! And agreed with @achrafmohye, you shall create a new issue to do the suggestion made by @Synar

[RomainValls]

Created this issue for the typecast : #10805