separate spec-generation from mojo-ising

preaction / Yancy

The Best Web Framework Deserves the Best Content Management System

http://preaction.me/yancy/

Other

54 stars 21 forks source link

separate spec-generation from mojo-ising #27

Closed mohawk2 closed 6 years ago

mohawk2 commented 6 years ago

This is a further step towards separating out the OpenAPI spec. Any further and it will clash with #26.

Next steps as far as I can see would be:

allow the supplying of an OpenAPI spec, documenting the (current) limitations of that
separate out the editor into probably Yancy::Controller::Yancy::Editor (I confess I think the naming of Y::C::Y::API is Ok)

coveralls commented 6 years ago

Coverage increased (+0.06%) to 98.69% when pulling 1360c8a0adfb95fca4d70e504d4ef10d32144eee on mohawk2:openapi-separate into 7f8050e4407d4e9e629dfeacf5fe1884f2bde518 on preaction:master.

preaction commented 6 years ago

Looks good to me, thanks!