aboutsummaryrefslogtreecommitdiffstats
path: root/app/javascript/vehicle_journeys/containers
AgeCommit message (Collapse)Author
2018-04-25Refs #6779; Fix diabled buttons in archived referentials6779-fix-info-button-on-vjs-editorZog
2018-04-25Refs #6472; Add Constraint Zone exclusions to journeys6472-itls-exclusionsZog
along with the React interface
2018-03-15Refs #6143; Configurable extra headers on VJs editorZog
2018-02-27Refs #6063; Fix the journeys time editor6036-fix-journeys-editorZog
2018-02-02Refs #5825 @1h; Fix info window behaviour on VJs editorZog
2018-02-01:fire: log5798-show-return-times-on-vjs-editorZog
2018-02-01Refs #5798 @3h; Show return journeys on the journeys' editor.Zog
2018-01-31Merge pull request #269 from ↵Luc Donnet
af83/5574-vehicle-journeys--fix-transporter-deletion-in-modal--rb 5574 vehicle journeys fix transporter deletion in modal rb
2018-01-31VehicleJourneys#index: Allow company deletion in 'add' modal5574-vehicle-journeys--fix-transporter-deletion-in-modal--rbTeddy Wing
While the 'x' button in the Select2 was available in the 'edit' modal for a vehicle journey, it was not in the 'add' modal. Thus, once you added an associated company, you couldn't remove it in the modal. You'd either have to cancel and create your vehicle journey again, or create it an delete the company in the 'edit' modal later. This enables the 'x' button in the 'add' modal (it previously was only enabled when `editMode` was active) and sets the proper action/reducer to remove the company. The `allowClear` attribute was changed to only work in the 'edit' modal in 0079238842263768b88b0fa0fd977824b49eabd5. That commit appears to be changing things so that certain functions work when not in 'edit' mode. The case we're concerned about is that the 'edit' modal can be opened when in 'view' mode (not 'edit' mode) in order to get more detailed information about a vehicle journey. This means the company Select2 is available in 'view' mode, and the 'x' button should not be visible in that case. But, when I tested this, even with `allowClear: true`, the 'x' button wasn't visible. This, I can only assume, is because the Select2 is in a 'disabled' state, so it's smart enough to know not to show the 'x' button. Which works great for us, because this allows us to not show the 'x' button here and still show it in the 'add' and 'edit' modals. Refs #5574
2018-01-29Refs #5750; Add a validation on VehicleJourneysZog
Ensure a time is set for all non-commercial stops
2018-01-11Refs #5551 @0.5h; Implement the custom fields in the creation modalZog
And Refactor the component in the process
2018-01-09Refs #5502 @4h; Don't use Ajax in JP selector in VJs editor5502-remove-search-from-selectsZog
When the number of possible values is low (<10), display the values right away, don't use an Ajax query
2017-12-27Refs #5407; Add cancel button on VehicleJourneys editorZog
2017-12-27Refs #5407;Zog
:fire: useless code Rename some vars
2017-12-27Refs #5407 @4h; First UI implementationZog
- Add most of the react code - And the specs where possible Still remains: - Link PurchaseWindows to VehicleJourneys in the model - Add an autocompletion endpoint
2017-10-30Refs #4795cedricnjanga
Show the tools buttons even if editMode = false The only buttons activated (if a vj is selected) are info, timetable and notes We then change the behaviour of the modals depending ont the context (editMode or note)
2017-10-06Add vehicle journey appcedricnjanga