cljdoc

https://cljdoc.org/ & https://github.com/cljdoc/cljdoc
noprompt 2019-09-13T21:41:38.069800Z

I ran into the error I encountered a couple weeks ago and opened a ticket for it: https://github.com/cljdoc/cljdoc/issues/349.

noprompt 2019-09-13T21:42:29.071Z

Today I’m busy with a few things but I want to collaborate on this issue. 🙂

noprompt 2019-09-13T21:43:01.071600Z

With a little direction, I can submit a patch.

martinklepsch 2019-09-13T21:45:20.072600Z

Thanks @noprompt, we’ll try to provide some pointers soon! :)

noprompt 2019-09-13T21:45:52.073100Z

Yeah, just let me know what the shape of that data should be and I’ll put together a patch for it.

noprompt 2019-09-13T21:46:54.074300Z

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.

noprompt 2019-09-13T21:47:46.074700Z

Just assume anything that comes from the user to be a hot mess. 🙂

martinklepsch 2019-09-13T21:59:44.076800Z

Totally agree, we have error tracking in sentry but I guess time has been lacking to really address all language level exceptions 😬

noprompt 2019-09-13T22:01:41.077300Z

No worries man! I wanna help.

noprompt 2019-09-13T22:02:20.078200Z

I totally sympathize with the time thing. This seems like some low hanging fruit and I can make the time to pick it.