-
Notifications
You must be signed in to change notification settings - Fork 84
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
Provide diagnostic information when plugin loading fails. #51
Comments
Would it not be enough to print out the list of available plugins in these cases? |
Any namespace on the classpath could potentially be a plugin, so that's not really feasible. |
Can this be assigned to me? |
That would be great @noorfathima11 , thanks for looking into this. You'll find the code in First we try to load the plugin namespace based on the plugin name. How it does this depends on what kind of name the plugin has. If it's a namespaced (qualified) keyword like If it's a simple keyword that contains a period then we load the corresponding namespace, so This namespace loading completely ignores all errors, it really doesn't care if it finds a namespace or not, it proceeds regardless. The namespace that we try to load is expected to contain a So to give better diagnostics this code is going to have to become smarter. In For example:
I hope that makes sense... let me know if you have any questions! |
Hi @noorfathima11 , I've unassigned you so others can take this up if they want you. Do let me know if you still want to try your hand at this or other issues. |
Fixed by #181 |
A follow-up to #35 / #42. Currently when a plugin isn't found, this is what it looks like
It would be good if we could give the user some kind of indication of what might be going wrong.
The text was updated successfully, but these errors were encountered: