adding abillity to define services imperative

[delijati]

See issue #334 for more info. Coverage for sphinxext increased to 60% :)

[almet]

consider: "Here is an example of how to define cornice resources in an imperative way"

[almet]

Hi!

Thanks for taking the time to submit this pull request. That's appreciated. I like how the decorators are now completely optional, and in some way, it closes the gap I started to fill when I did the cornice refactor.

I'm not a big fan of the add_resource and add_view names, but they seem to match with the ones provided by pyramid itself, so I think it's fine to let it like that.

I've added a few comments and I think we're good for merging once they're addressed.

[delijati]

Hi,

i've added the directive add_cornice_resource to get rid of the scan. There is still that issue with ordering of the resource views. I think a cleaner way would be to add a Register Object like the Service object witch holds the collected informations. But this should be done in another refactoring ;)

[delijati]

Do you had some time to look into that?

[delijati]

@leplatrem could you also take a look into that pull request

[almet]

Hey Josip, this looks really good. Eveything is in there: impelmentation, docs, new tests, plus the old tests are passing.

Let's merge :-)

[delijati]

Wonderful do you know if someone is already working on the push request #285 ? If not i will look into that one next week.

[almet]

Neat. Nobody is currently working on this I believe. Feel free to take it!