Do not create operations for non-HTTP methods/verbs

[whitlockjc]

For path properties that are not HTTP methods/verbs, do not process them as Swagger operations.

Fixes #678

[webron]

@whitlockjc - we're going to add support for the 'search' http method soon. will that require an additional change?

[whitlockjc]

That is correct, you'd add 'search' to the list of HTTP method/verbs in the array. The idea here is to only process the real HTTP methods/verbs instead of assuming all path properties are HTTP method/verbs like is happening now. I chose the simplest approach to convey the fix but you can do with this however you want.

[webron]

It's not like I know how to do it any better ;) Just wanted to make sure. By the way, patch is already supported by the spec. I just assume that path in the PR is a typo.

[whitlockjc]

I updated the previous comment to use 'search' instead of 'patch'. As for 'path' being used instead of 'patch', that's a typo and I'll fix it and update the PR. Would you like me to add 'search' to the list during the process?

[whitlockjc]

I've updated the typo and left out 'search' for now since that is an upcoming change.

[webron]

Let's follow up OAI/OpenAPI-Specification#133 regarding the search option.

Out of curiosity, wouldn't it be 'safer' to say whatever is "not" x-?

[whitlockjc]

Well, you'd also have to do that for parameters and other legitimate operation properties, something that could change over time while the supported list of HTTP methods/verbs will likely stay mostly static. I think the approach in the PR is pretty good, although the list of supported operation HTTP methods/verbs could be refactored into a variable elsewhere.

[webron]

👍