-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
compute paging error #352
Comments
This is valid issue for ListUsagesResult of Usage_List. containerService.json is in correct format. |
Can you please verify whether Usages_List is truly pageable? Does it support nextLink? The extension has been defined with nextLink however the model UsagesListResult does not have nextLink as a modelProperty. If this is not a pageable operation and you still want flattening (IEnumerable) to be returned then please explicitly set nextLink property of the x-ms-pageable extension to null. Check the docs over here. If it supports nextLink then please add nextLink as a property of the corresponding model. |
I will check with the team, but this spec was converted from the Hyak->Swagger tool by your team, so maybe the bug (if any) is from there. BTW, can the code gen tool not enforce the check? |
The hyak to swagger converter was not 100% accurate and it just gave the service teams something to start with rather than service teams writing the swagger spec from scratch. This bug was caught as a larger goal of creating a linter for the spec. Now that it has ben caught, please make sure to resolve this at the earliest. |
That's a very valid ask, and we would double check it, and fix it. But instead of ad-hoc check and fix, can you do a sweep check on the big specs, so that we can fix them all? Thanks. + @hyonholee |
As I said this is a part of a larger goal. The Swagger spec linter (winter) is coming !! #GOT ;) |
The usage list API doesn't seem to be pageable, but some others with this property defined do not seem to work properly in AutoRest generated Node.js SDK & thus CLI. Please refer to: |
Close this one, it's ok now. Thanks all! |
The compute composite Swagger file has an error
The latest codegen enforce the check for paging extension to make sure there has a property in the response to match the property name specified in extension.
This file presents an error on Travis.
The text was updated successfully, but these errors were encountered: