require_dataset() uniformly raises NoDatasetFound #6521
Merged
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.
Before it claimed to raise InsufficientArgumentsError uniformly,
but actually raised NoDatasetFound or ValueError, depending
on the exact error condition.
This change consolidates and documents raising NoDatasetFound,
which seems to make most sense.
Changelog
🐛 Bug Fixes
require_dataset()
now uniformly raisesNoDatasetFound
when no dataset was found. Implementations that catch the previously documentedInsufficientArgumentsError
or the actually raisedValueError
will continue to work, becauseNoDatasetFound
is derived from both types. Fixes datalad-configuration dump not working without dataset #6503