-
Notifications
You must be signed in to change notification settings - Fork 64
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
Clearer error messaging for undefined keys #111
Comments
That looks like a regression. When you say "IG failed" can you give me the function that failed? Or a more complete stack trace? i.e. were you trying to |
A reproduction of the error message and stack trace, but for a specifically bad integrant EDN configuration entry named ...
:blargh {}
... On the off chance it's germane to this issue, aero is being used to pre-process that EDN file. Barf from that java process:
And that report file:
|
Thanks for the stacktrace, but that looks like a different error. Do you have a stacktrace for the original error? |
I apologize, yes, the key needs to be namespaced to reproduce the original error. Here it is: File :admin/blargh {} Console output:
Snippet from report file:
|
I was adding in some new components into an Integrant configuration, and took the opportunity to see how Integrant reacts to keys being specified in the conf file but not implemented. Given
IG failed with:
I think a better error message here would speak directly to the cause, for example:
Like Figwheel, it might even go on to suggest clues to assist in remediation, such as the fact that the key wasn't registered with IG using
defmethod
, noadmin
namespace was found, no symbol:admin/jetty
was found in a presentadmin
namespace, and so on..The text was updated successfully, but these errors were encountered: