Brian Terlson
Brian Terlson
Folks chiming in for AsyncAPI support, please feel free to link your AsyncAPI specs if they are public, it would be great to take a look!
Nothing new to share, unfortunately. Keep chiming in with support, though!
I don't think we want to allow name conflicts (otherwise references need to become version-aware, or references would need to resolve to some kind of version record instead of a...
What are you thinking for optional properties? `prop foo?: T`? Also I wonder if we should consider this as part of `Optional` where `{ x?: string }` and `x: Optional`...
What is an int32 enum? OpenAPI doesn't have that concept I believe. Are you wanting to see a particular output in some other emitter?
JSON Schema doesn't define that format afaict, so I'm actually a little confused why we generate it in the first place. @mikekistler any thoughts? Is this something we should even...
It doesn't define the int32 format specifically though. While the spec allows for arbitrary values, it seems weird that we would include a format that most (all?) implementations wouldn't support....
Another option: admit @willmtemple was right and use `satisfies` for the current meaning, and `extends` to mean that each variant must literally extend the given type.
I think we should be clearly separating features in 3.1 which we do not support intentionally (and thus are feature requests not bugs) and things which impact 3.0 which we...
Proposal: add a new decorator to the OpenAPI library called `tagMetadata`. It MUST be applied to the service namespace, it is an error if it is applied to any other...