New documentation for v0.4.0 release

[maxlinc]

No description provided.

[coveralls]

Coverage decreased (-1.38%) when pulling c7d6a32 on v0.4.0_docs into b061db5 on master.

[coveralls]

Coverage decreased (-3.05%) when pulling c7d6a32 on v0.4.0_docs into b061db5 on master.

[coveralls]

Coverage decreased (-3.05%) when pulling ef436c6 on v0.4.0_docs into b061db5 on master.

[bf4]

looking good. I've been going through the code trying to figure out how to use my swagger public/api-docs.json as a contract and also for code generation a la prmd and heroics (ref: heroku api toolchain) and maybe even something like a json validation middleware.

one hiccup I've come across is that pacto is optimized for consumer driven contracts, where you have a service, and you want to generate contracts from its behavior. This can't (easily) work for me as I'm testing my apis using rack-test, and no requests are actually made.

I've been interested in documentation-driven contracts (which pacto references) wherein I spec out a swagger resource when I can then use as a contract, for code generation, etc., but this approach doesn't seem supported in any libraries I've seen. The new Pacto::Formats::Swagger seems to be the most likely candidate to go in that direction.

[bf4]

I'm guessing pacto isn't under active development any more?