Add actions for timetables API /to-combine endpoint

[Leitsi]

This change is 

[jarkkoka]

f

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @Leitsi)

---

metadata/hsl/actions.graphql line 37 at r1 (raw file):

input ToCombineTargetVehicleScheduleFrameIdInput {
  stagingVehicleScheduleFrameId: uuid!

I'd like to have all these combine/replace definitions be consistently defined in the same order. For example, toCombineTargetVehicleScheduleFrameId comes before toReplaceVehicleScheduleFrameIds, but at the end of this file, the order is reversed.

---

metadata/hsl/actions.yaml line 62 at r1 (raw file):

    - name: ReplaceTimetablesInput
    - name: ToReplaceVehicleScheduleFrameIdsInput
    - name: ToCombineTargetVehicleScheduleFrameIdInput

I think combine defintions should be consistently before "replace"s to help the code reader.

[Leitsi]

Reviewable status: 0 of 2 files reviewed, 2 unresolved discussions (waiting on @jarkkoka)

---

metadata/hsl/actions.graphql line 37 at r1 (raw file):

Previously, jarkkoka (Jarkko Kaura) wrote…

I'd like to have all these combine/replace definitions be consistently defined in the same order. For example, toCombineTargetVehicleScheduleFrameId comes before toReplaceVehicleScheduleFrameIds, but at the end of this file, the order is reversed.

Fixed. The order might've just come from Hasura since these were created via the UI.

---

metadata/hsl/actions.yaml line 62 at r1 (raw file):

Previously, jarkkoka (Jarkko Kaura) wrote…

I think combine defintions should be consistently before "replace"s to help the code reader.

Done.

[jarkkoka]

Reviewed 2 of 2 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Leitsi)