Closed NobbZ closed 9 years ago
I went through my commit log and found that contracts
-gem went from 0.7 to 0.8 in some of my expermints last night. After downgrading it worked again.
So the issue is: yard-contracts
does not work with current version of contracts
-gem
Yep, this was silly on my part. I made some improvements to Contracts for yard-contracts to make use of. While waiting for them to be merged I duplicated them in yard-contracts. But then they diverged and became incompatible so when a new Contracts was released with my changes it broke yard-contracts. I've just removed the duplicated stuff from yard-contracts so it's all working again and I've pushed a new version to Rubygems.
Contracts 0.8 and yard-contracts 0.1.5 should now work together so I'm closing the issue. Let me know if you have any other problems.
Using 0.1.5 does work with contracts 0.8, thank you for the quick response!
All of a sudden
yard-contracts
stopped working with the following stacktrace, even without loading it explicitely:The actuall content of
~/.yard/config
is:If I change
:load_plugins
tofalse
I don't get an error anymore, but of course yard-contracts doesn't work then ;)The way I use
yard
andyard-contracts
in my project is:And then simply run
rake doc:app
, but this problem does occur even outside of the project. Theyard config
that produced the output above was run from$HOME
.If I uninstall
yard-contracts
yard config
shows the actual content of~/.yard/config
, also this problem does occur independently of which version ofyard-contracts
is installed, I tried "0.1.2" and "0.1.4" which both worked yesterday.All what changed was, that I tried to use
yard-doctest
, but I removed it completely because it wasn't able to test my project because of the use of selfdefined tags and the presence ofContract
s ;)