Drtii 1667 spike acl origin not always matching api origin #1976
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ching-API-origin # Conflicts: # project/Settings.scala
ngu04
approved these changes
Jan 9, 2025
Origin is where the flight began, previous port is the last port it took off from. I guess a flight should only have one origin |
richbirch
deleted the
DRTII-1667-SPIKE-ACL-origin-not-always-matching-API-origin
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use arrival's new previous port field to match API manifests when different to the origin
Display previous port in feeds popup for each arrival
Rename
ArrivalKeytoManifestKeyas that's the only thing it's used forRemove a lot of dead code