Farren Casad

Yep, that is exactly what I want to do. It does work with the tooling I'm using, but my team was concerned since this isn't mentioned in the spec.

@webron thanks. Are you aware of any technical reasoning against supporting this? And if not, what would it take to add to the spec?

Appreciate the insight! I agree a potential `#/components/operations` is probably not particularly helpful for reuse, but by that token is `#/components/pathItems`? Btw, my goal isn't to reuse an operation within...

Ok, it's understandable to try and avoid increasing the spec surface area. But splitting at the path item level isn't really ideal to me. I'll consider alternatives...

Hi everyone, Sorry you were affected by the regression in 4.10.4! It should be resolved in 4.10.5.

Re-visiting since a few other folks asked for this... I've now seen several large OpenAPI documents in the wild that have made this (non-canonical) use of $ref. One public example...

Note to whoever picks this up - the global prism config has 'validateRequest' and 'validateResponse' defaulting to true so we can mirror this on a per-request basis. Also let's use...