-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priority system in loaders no longer works #584
Comments
Those are passed as kwarg to |
The loader priorty is stored here, but it looks like we need to be more specific about using it (before, it seemed that the order in the registry was part of the determination for which loader to choose). It seems at some point, we took them out during a refactor. I'm imagining that we'll want to find all loaders that meet the identifier criteria. If there is more than one, simply compare priorities and return the appropriate loader. |
This is fixed by #757. |
Loaders are assigned priorities and they should be taken into consideration when conflicts arise amongst potential loaders when a format is not explicitly give.
The text was updated successfully, but these errors were encountered: