-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PagerDuty REST Api generation fails #591
Comments
Thanks for filing this. An easy bug and a harder bug here. The easy bug is that progenitor, amazingly, doesn't handle the schema Once I fixed that, I found the second problem: there are a bunch of what I'll call "unexpected" references. Here are some notable examples:
Most OpenAPI documents limit this references to paths of the form: My first suggestion is to pre-process the file to either inline these weird references (taking care not to fall into a cycle) or pull them out as top-level Note to self: https://swagger.io/docs/specification/using-ref/ explains the |
Thanks for looking into this! |
Just tried re-running this with the latest git code and 0.6.0 returning now only this error:
But I see it in the json file:
|
I'm trying to use
progenitor
to generate a PagerDuty API client using their published OpenAPI v3 spec from here openapiv3.jsonI have these dependencies in my
Cargo.toml
:And a simple
lib.rs
:However when running
cargo build
I get this error:The text was updated successfully, but these errors were encountered: