Harmonize comfort types #8254
Labels
area:editoast
Work on Editoast Service
area:front
Work on Standard OSRD Interface modules
kind:enhancement
Improvement of existing features
Description and goal
With Trainschedule v2 model, we now use the type
Comfort
to define the comfort of a train in stdcmV2 and trainscheduleV2 (TrainScheduleBase
type) endpoints.The old model was using type
RollingStockComfortType
. Most of it will be removed when dropping v1 model.But in rollingstock endpoints, we keep using this old type for effort curves and it should be harmonized with the new model.
Acceptance criteria
RollingStockComfortType
is removed from the code baseAC'
instead of'AIR_CONDITIONING'
should be removed (including trads)Comfort
is now used for all rolling stock endpointsTrainScheduleBase
useComfort
for itscomfort
propertyThe text was updated successfully, but these errors were encountered: