-
-
Notifications
You must be signed in to change notification settings - Fork 228
Bug on parsing config.yml file #538
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
Comments
How strange 🧐. 0.10.6 added support for JSON config files, this must have broken something with YAML. We use a |
Indeed, those fields are not used in the end2end tests... |
@dbanty any thoughts? |
I had the same problem. For me it works to use the absolute path to the config file. Windows 10 |
I was getting same error on both json and yaml file. This worked for me too. macOS Big Sur Version 11.6 |
Interesting, it must be a problem with the content type detection. I thought we were converting to absolute paths before parsing internally but maybe not. Glad there's a workaround for now, but obviously this still needs fixing. |
We upgrade the version from 0.10.5 to 0.10.7
While we trying to generate a client with a config file the process failed
openapi-python-client generate --url=http://localhost:8000/latest/openapi.json --config=config.yml
Without the config file, it works perfectly
The config file content:
The issue does not appear in 0.10.5 version
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: