Skip to content

Display the GOV track in the correct order and with the local track names #14229

@hamz2a

Description

@hamz2a

Adapt the operational points schema:

OperationalPointPart {
    local_track_name:   "V1"
    ...
}
  1. Perform a migration.
  2. Update the schema.
  3. Update the Python side (schema + generator).

Notes:
To fix the bug, you must first run the migration, then correct the issue based on the data import.
During the migration, instead of leaving the field empty, you should reuse the value from the track.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Awaiting merge

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions