Fix bug in creation of default identifiers for data loaders #447
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.
Prior to this PR, if no identifier or list of compatible extensions was provided to the
data_loader
decorator, then an invalid identifier would be created. This fixes that bug and also adds more informative output for these cases.It's worth noting that
specviz
now expects all loaders to have identifiers. So if a user creates a custom loader that has neither an explicit identifier nor a list of compatible extensions, it will not be possible to load the associated files usingspecviz
.We may want to consider adding an optional argument to
data_loader
that automatically creates a dummy identifier that positively identifies all files.Thanks @nluetzge for providing the original bug report.