Hi,
I put up a screenshot and a it now will show a little bit of "unimportant"
stacktrace near the "important" stuff. Please let me know if you have any
more ideas. Bump your version to 0.2.2.
thanks,
Jake
On Friday, September 13, 2013 12:21:00 PM UTC-6, Christopher Allen wrote:
>
> Link:
>
>
Hi,
I put up a screenshot and a it now will show a little bit of "unimportant"
stacktrace near the "important" stuff. Please let me know if you have any
more ideas.
thanks,
Jake
On Friday, September 13, 2013 12:21:00 PM UTC-6, Christopher Allen wrote:
>
> Link:
>
> https://github.com/jakepears
Thanks for putting this plugin together, very useful!
A couple of remarks:
- Seems to the advantage over aphyr/prism in terms of not forcing you to
use the foo-test convention, for those of us who are keeping same names as
the namespaces in the test/ folder. It's possible I'm being non-i
Hi,
I added a screenshot to the readme. I think in general filtering items
from the stacktrace is a good idea, but I am probably doing it too much. I
have an idea. I will work on it this weekend.
thanks,
Jake
On Friday, September 13, 2013 12:21:00 PM UTC-6, Christopher Allen wrote:
>
> Link:
Hi,
Quickie is a leiningen plugin to autotest clojure.test tests. There don't
seem to be any active projects for clojure.test, so a couple of people at
my office wrote one. Please let me know if you have any problems or ideas:
- Uses the builtin clojure.test test runner so you don't need to
Link:
https://github.com/jakepearson/quickie
Is it possible to see *some* of the stack trace so you can debug?
Also you should include a screenshot of what the library looks like in
action. :)
On Friday, September 13, 2013 10:57:35 AM UTC-7, Jake Pearson wrote:
>
> Hi,
> Quickie is a leininge
