GitLab

Forward declaration seems not to be enough for MSCV

See https://binary-factory.kde.org/view/Windows%2064-bit/job/KTrip_Nightly_win64/447/console

Simplifies working with transport API upstream by reducing implementation
magic.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This produces sensible journey and departure responses now, if the backend
doesn't respond with an error.

Some of those contain wrapped XML and JSON content, one of those is the
vehicle layout. We still need to find a way how to expose that from here.

Their mgate backend returns too many errors still to switch from the old
Hafas protocol still.

This gives us flexibility for deviations and exceptions we cannot
otherwise match correctly. As our file names are used as settings
keys we cannot arbitrarily rename them at this point.

This adds compatibility with our translation system and the line mode
mapping we need.

Still needs a few more changes to fully align our format before this
begins to be fully useful.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Not used by our code yet, but brings us further in line with the upstream
transport API format.

This uses the correct GeoJSON format for areas, but still doesn't qualify
coverage areas correctly, nor does it add the ISO 3166-1/2 region data.

Will be needed for moving the backend service config file format to the
standardized transport API format.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

was missing a couple includes

CCMAIL: vkrause@kde.org

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

These seem to be often duplicates, so removing those helps in dealing with
that as well.

There seem to be duplicates in the results occasionally, with the same id
but different source id and very different position. This gets merged here
and then makes matching against OSM data fail. Instead we now prevent
merging here by including the source id in the identifier, and instead let
OSM matching sort this out.

This gives us aggregated real-time status data for station equipment.

This seems to happen occasionally as transient state from assigning stuff
from QML. Prevents sending out nonsense queries to backends.

Both GBFS and OTP provide that distinction (at least somewhat), and now we
can actually represent that.

This replaces the hard-coded support for rental vehicle docks by a
QVariant. For rental vehicle docks nothing changes, but we can now
also represent floating rental vehicles properly, as well as station
equipment like elevator or escalators.

API/ABI doesn't change, but UI code will need adjustments to make full
use of this.