Allow Schema definitions via decorator about flama

[perdy]

One of the goal I had in mind when I started to work in this framework was to keep a balance between the complexity of the core codebase and the value it adds to the coder (i.e. increase expresiveness and simplify the coding job).

In my opinion this is a minor gain in front of the major changes we need to add to the user flow and to the injection mechanism. We now force the user to decorate the endpoint and that's opposed to the idea of using the python's typing to keep the app's codebase simple.

Maybe we can consider this kind of behavior as a plugin to enrich the framework features to those users that wanna do the trade off.

[mvanderlee]

The decorating is optional, not forced. All it does is allow you to override the schema.
If no decorator is defined, it will use the type hint as before.

If you still do not want this, I'd at least like to see integration of the marshmallow-dataclass detection that I've added. That would solve most of my use cases.

[migduroli]

Closing this issue, as discussed on the PR related to it. We think this is no longer applicable due to the heavy refactoring Flama has gone through over the last few months. We really appreciate the effort @mvanderlee. I would suggest you to check the new documentation, and the new version recently released, 1.3.0. I think this issue is already resolved. If not, we're happy to re-think about it. Please, let's discuss if beforehand if so, as we're planning more enhancements over the next months, so that we don't duplicate efforts.
Thanks!