Prevent importing unsupported tracker from backup #944
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
This will lead to graphql field validation errors (non null declared field is null) once the track records get used, since they will point to trackers that do not exist
schroda
force-pushed
the
fix/handling_of_unsupported_trackers
branch
from
6c66e98 to
d9c6a5f
Compare
Was already partially changed in 7df5f1c but this occurrence was missed
schroda
changed the title
Syer10
approved these changes
May 6, 2024
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.
This will lead to graphql field validation errors (non null declared field is null) once the track records get used, since they will point to trackers that do not exist