We can always add a debugger
, and run it use crystal i
, it works.
But, my concerns is, how to do same thing when run crystal with crystal spec
?
We can always add a debugger
, and run it use crystal i
, it works.
But, my concerns is, how to do same thing when run crystal with crystal spec
?
Just run the specs with crystal i
. The spec
command doesn’t really do anything substantially different. It’s mostly convenience features like implicitly requiring an entire directory tree. You can’t have that with crystal i
, but you probably don’t need it when you want to run a specific spec in the debugger.
Eventually I’d like to add an i spec
or speci
command for that.
It works! i really should be think of it.
$: crystal i spec/some_spec.cr