ignore the destinationText of a leg until this is correctly returned … #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the logic for fetching the next trip is not working correctly because the backend doesn't provide a consistent "destinationText" (this bug is still open openTdataCH/ojp-sdk#198).
In the meantime we can fix this in the SDK and ignore the destinationText from the hash.
Also in order to have more robustness I think that is better to use the ids instead of the name for the leg stations.