Built using Ruby's TracePoint API and type information from YARD (cc @lsegal)
-
-
I had thought of writing this tool. You've written a better implementation than I would have!
1 reply 0 retweets 1 like -
Thanks! It bugged me every time I ran into stale YARD docs. The metadata is easy to get via YARD couldn't believe there wasn't a solution.
1 reply 0 retweets 0 likes -
Replying to @backus
My tests are all in Minitest. I don't suppose that would work with this eh?
1 reply 0 retweets 0 likes -
Replying to @6ftdan
1/ It doesn't but it could be adapter for that in the future. Right now it basically just invokes rspec's runner.
1 reply 0 retweets 0 likes -
2/ I wrote it to enable method tracing around each example. This makes it not unbearably slow. Would need to find equivalent for minitest
1 reply 0 retweets 0 likes -
Replying to @backus
Have a look at my gem state_inspector https://github.com/danielpclark/state_inspector … … it uses the method decorator pattern to observe method calls.
1 reply 0 retweets 0 likes -
That might give you much better performance.
1 reply 0 retweets 0 likes -
Replying to @6ftdan
Neat I'll check it out. Have you benched it against using `TracePoint`?
1 reply 0 retweets 0 likes -
Replying to @backus
No… TracePoint is still something I've never tried. I do know my example at the end recorded ~8000 method calls to a log in little
1 reply 0 retweets 0 likes
Nice. `TracePoint` is pretty simple you should check it out. I extract parameter values in 4 lines of code! https://git.io/vSkot
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.