Add TagNotFoundError for tag misses in Bazefetcher #199
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
Being able to detect and recover from missing tags is quite useful for downstream users working with multiple similar-but-not-quite data sources. By adding TagNotFoundError, users can mechanically determine if this is a soft input error (missing tags) that can be recovered from, or more severe errors that require aborts.
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.
Being able to detect and recover from missing tags is quite useful for
downstream users working with multiple similar-but-not-quite data
sources. By adding TagNotFoundError, users can mechanically determine if
this is a soft input error (missing tags) that can be recovered from, or
more severe errors that require aborts.