Skip to content
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

Remove the auto-detection support of spec format and always use config SPEC_FORMAT #67

Closed
greyli opened this issue Jun 18, 2021 · 0 comments · Fixed by #69
Closed

Remove the auto-detection support of spec format and always use config SPEC_FORMAT #67

greyli opened this issue Jun 18, 2021 · 0 comments · Fixed by #69
Assignees
Labels
Milestone

Comments

@greyli
Copy link
Member

greyli commented Jun 18, 2021

The SPEC_FORMAT config was re-added via #66. To keep the inconsistency, the spec route should also use the value of SPEC_FORMAT.

Currently, the format will be decided based on the spec path. For example, if the spec path is foo.json, then the JSON format will be used, while the YAML will be used if the spec path is foo.yaml. This behavior will be removed in 0.7.0, now the format should be set explicitly with the SPEC_FORMAT` config.

@greyli greyli added this to the 0.7.0 milestone Jun 18, 2021
@greyli greyli self-assigned this Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant