-
Notifications
You must be signed in to change notification settings - Fork 85
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
Seemingly unreasonable lower_snake_case case convention on component properties #121
Comments
@SidneyJiang We understand that different users may have different needs for case conventions, so the convention validated for is configurable. See the configuration documentation to learn how to configure the tool to use your own case convention. |
@dpopp07 I wonder if I change the configuration file, how should I serve my |
As long as the file exists in the folder you are running the command from (or in any parent folder), you should have no issues |
Also I looked at the linked you pointed me, I can't figure out how can I just turn off lower_snake_case for |
Thank you very much, I will close this issue |
The component section the the APIdoc describes either what the request payload looks like or what the response payload looks like.
Different team defines the payload properties differently. As in our pipeline, the payload properties always follow Camel case convention.
So they look like the followings:
or
As a result, when we use validator to validate our apidoc: https://dev.console.test.cloud.ibm.com/devops/pipelines/tekton/apispec/openapi.yaml?env_id=ibm:ys1:us-south
it complains
pipelineRunId
,envProperties
violates lower_snake_case rule.However, I think the property is totally legit.
The text was updated successfully, but these errors were encountered: