Make write_raw_bids() raise if an unsuitable extension is provided in the BIDSPath #1053
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.
Some extensions / formats are only allowed for certain data types, e.g.
.vhdr
is (i)EEG-only.When passing a
BIDSPath
containing bothdatatype
andextension
towrite_raw_bids()
, in case of a mismatch we would previously simply silently replace the incorrectextension
, effectively writing to a location (and file format) the user didn't expect.We now raise an exception in such situations.
Fixes #1041
Merge checklist
Maintainer, please confirm the following before merging.
If applicable: