There is now a distinction between no security being defined by operations, and empty security requirements. If the `Security` value is `nil`, then it was left out.
If the slice is empty, it was defined and left empty by design. As requested by #111
Signed-off-by: Dave Shanley <dave@quobix.com>
The v3 model is wrong and out of sync with the spec. It's been corrected, so the v2 and v2 model for SecurityRequirement have been collapsed down into a base model., they are the same data structures. This has allowed me to delete the complexity of sharing two different models for the same structure, by unifying the model correctly. I am not sure why I decided to change the v3 model, oh well, its been corrected. Long live swagger!
3.0 and 2.0 do not work, there are multiple versions and anything with a period in it sucks from my point of view, v2 and v3 feel much better from a DX perspective.
