FIX: Exclude non-Hashables from set in .get(return_type='id') #948
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.
Fixing a bug I introduced in #942
The problem is that just getting the raw
.entities
variable from aBIDSFile
will return everything, including meta-data (which is arguably a design flaw).The problem if anywhere in the meta-data you use the same name as a BIDS entity (in my case it was
task
), its returns will also be returned.This simple fix check if at least the input to
set
is not Hashable, to prevent an error (although it will still return something funky if a non-hashable result from meta-data sneaks in).