Skip to content

Separate path_helper and operation_helper logic in web framework plugins #17

@lafrech

Description

@lafrech

Issue by sloria
Monday Jul 30, 2018 at 00:44 GMT
Originally opened as marshmallow-code/apispec#257


From #246:

Also the web framework path helpers deal with operations quite a lot, and perhaps this logic should be split into path_helper and operation_helper. From a quick glance, the coupling between the two seems loose. Could be a bit trickier with flask due to the if method in rule.methods test, which covers what looks like a twisted but legit case (method declared in the view but not in the rule).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions