-
Notifications
You must be signed in to change notification settings - Fork 9
fix(openapi): Fix #107 - Class Names are in SNAKE_CASE but should be … #108
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
base: main
Are you sure you want to change the base?
fix(openapi): Fix #107 - Class Names are in SNAKE_CASE but should be … #108
Conversation
…ut should be in CamelCase
|
pending to review API version (and path) and AP testplan modifications |
Co-authored-by: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com>
Hi @jgarciahospital, |
|
Hello @jgarciahospital @sachinvodafone @maheshc01 |
|
Please ignore my another github user (@CampusOxide) approval on this |
|
Hello, path updated to /vwip as requested by @jgarciahospital |
This is another account of Sachin' so please ignore this request.
albertoramosmonagas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Some Class Names are in SNAKE_CASE but should be in CamelCase
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR fixes issue #107 by renaming classes and of course increments spec version
Which issue(s) this PR fixes:
Fixes #107
Special notes for reviewers:
Only changes NO_DATA, LOW_DENSITY and DENSITY_ESTIMATION class names
Changelog input