Drew Powers

> Also we need to produce 2x or more amount of the code to support the both of usages with or without visibility, for each components, paths, and operations 🤯....

Looks great, and great tests! But let’s make this a `patch` release (just edit the `.changeset` file)

> But, do we intend to allow "partial aliasing" within the array value 👇 ? > > ```json > "layeredShadow": { > "$type": "shadow", > "$value": [ > "{simpleShadow}", >...

Yeah this is a tricky one but I’m open to adding whatever support we can here. Better than simply ignoring it altogether. I’m in favor of this approach as it...

Sorry—just realized I went a while without checking in on this. I’m happy with the direction of this PR, and we’ve discussed a lot of things outside of here 🙂....

This isn’t explicit, you’re right, but the root node is a group node. Any node that isn’t a token node (contains `$value`) is a group node. So any properties allowed...

> I was looking into the spec to slide in this bit of information. But I find myself not knowing where it would fit? I think this would be a...

Thanks for filing! You’re right—we should add a template for openapi-react-query. Though for now, it’s not an issue opening a bug against openapi-fetch because there’s still overlap in what those...

> I want to emphasize that this indeed is a bug which makes the library non-compliant with rules of HTTP protocol. Thanks for raising this. Ideally this follows the `fetch`...

Also as a temporary workaround, setting `createClient({ headers: { "Content-Type": null } })` should remove any default headers being sent, as an easier alternative to middleware, as a temporary workaround.