I ran into the error I encountered a couple weeks ago and opened a ticket for it: https://github.com/cljdoc/cljdoc/issues/349.
Today I’m busy with a few things but I want to collaborate on this issue. 🙂
With a little direction, I can submit a patch.
Thanks @noprompt, we’ll try to provide some pointers soon! :)
Yeah, just let me know what the shape of that data should be and I’ll put together a patch for it.
Essentially, any error that comes from Java or Clojure should be an error on behalf of cljdoc. If the user makes a mistake they shouldn’t hear it from Java or Clojure.
Just assume anything that comes from the user to be a hot mess. 🙂
Totally agree, we have error tracking in sentry but I guess time has been lacking to really address all language level exceptions 😬
No worries man! I wanna help.
I totally sympathize with the time thing. This seems like some low hanging fruit and I can make the time to pick it.