Drew Powers

Ah good catch @denisw—you’re right. No direct child of the `components` object should be potentially optional. 🤔 I’m surprised more tests didn’t throw, but I guess this just slipped through...

I’m going to attempt another fix to this; maybe we still see issues. But I think it’s an improvement? Happy to ship another patch or just revert this entirely if...

Also this is offtopic, but one thing I’m excited about for the v7 rewrite is what an AST lets you do: ```ts const allOptional = paramLocType.every((node) => !!node.questionToken); ``` In...

Yeah this may just need to be reverted. Optional objects are generally pretty friendly to use, but optional nested objects are not. Will revert the top-level parameters being optional and...

The upcoming v6.7.0 will revert to previous behavior where `parameters` is never optional, but `query`/`header`/`cookie` may be if they have no required params (path params are always required by their...

I’d be open to this! This is an easy add. Also if you do submit a PR, then make sure to update the corresponding docs that mention `x-enum-varnames` as well.

#1280 is unrelated and is on the typegen side; that won’t affect a runtime error like what you’re seeing. So I’m assuming that your API does **NOT** return a `204`...

It should also be noted that we respect the `Content-Length` header, so if your API sent `"Content-Length": "0"` then we wouldn’t try and parse JSON in that instance, either.

Thanks for the suggestion. I’m a little hesitant to deviate from the default fetch behavior too much, which this library implements. If this library throws, then `fetch()` itself threw, which...

We currently don’t support external refs. We’re currently thinking about a way to add it, as some refs may be remote, some may be local, some may require auth, per...