securitySchemes: not supported

[drahnr]

Currently when an openapi 3.0.0 spec contains a securitySchemes: and security attribute, it's not generating the appropriate code. It appears to be ignored entirely.

[drahnr]

I have proof of concept that works with header based API keys

[ahl]

Cool; can I see it?

[drahnr]

I wish I could, I'll re-create it soon™ - the btrfs volume it resided on got deleted during a system-upgrade for whatever reason and that branch wasn't backed up 😶‍🌫️

[drahnr]

@ahl see commit 0d3ccbf in #466 - I have to cleanup the mess at some point, it contains all the changes I needed for now and parts are not ready for inclusion

[tormeh]

For anyone who finds this: A possible workaround would be to make a new reqwest client for every request, add the authorization header as a default header, then make a new progenitor client based on that reqwest client using Client::new_with_client(url, reqwest_client).

(also bump)