Refactoring class based views

[borntyping]

Considering modifying the way routing is done to be a bit clearer, and avoid some of the mess of class-based routes. It'd look a bit like this[1]:

@entity.get('/profile', endpoint='profiles')
def get_all_profiles():
    ...

@entity.post('/profile', endpoint='new_profile')
@require_authorization
def new_profile():
    ... 

instead of like this:

@entity.route_class('/profile', endpoint='profiles')
class ProfilesView(MethodView):

    def get(self):
        ...

    @require_authorization
    def post(self):
        ...

A major advantage of this would be that endpoint and function names would be a lot more descriptive (as well as avoiding multiple endpoints under the same name), though it would result in having to repeat the route name (I'm not so sure this is such as bad thing). What do people think of this?

1. Note - we can already do much the same thing with @blueprint.route(..., methods=['GET']), which would be how this would be implemented internally.