Ron
Ron
Not sure this is something we should support because "these things exist". Haven't seen many people ask for it, and it feels like that's one of the few things about...
@dilipkrish That's just something I don't get. Your example shows a 200 response sending either Pets or Error - but how does that help the consumer? How would they know...
Heh, fair enough, it was my misunderstanding. Generally, I believe we have a similar view re your last comment.
Unfortunately, no. The headers in the responses is actually a new feature in 2.0, and we hadn't thought of the option to allow a global definition for it.
It's still an option we might consider in future versions.
Yeah, but this is not about reusability (which makes it easier) - it's about declaring it only once for all.
@darrelmiller did we not just talk today about disallowing Content-Type headers? :)
The spec just allows you to describe things. I don't think we should go into specific cases and start saying you can describe OAuth2 together with API Key but not...
Right, but I don't see a need to add that to the spec itself as a restriction. Other than marking it as a potential best practices documentation plan, there's not...