-
Notifications
You must be signed in to change notification settings - Fork 46
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
Migrate
@ 2020-01-01
- support for nonstandard next link
#492
Comments
@ziyeqf that's a Swagger bug which would need to be fixed - would you mind sending a PR to fix that? |
thanks @tombuildsstuff, but I may not get the point. If I submit a PR to rename |
@ziyeqf the Swagger should be defining As such just updating the API definition should be sufficient there, I don't think we need a Pandora change for this, I'm kinda surprised there isn't a linter to catch a field containing |
@tombuildsstuff I think it has been defined with I'm not familiar with the new base layer... But just found it's calling |
Got it, thanks - in which case yeah this is a bug in the new base layer here where we're relying on the OData value rather than using the value we're expecting: @manicminer mind taking a look into that one? |
Migrate
@ 2020-01-01
- support for nonstandard next link
Hey @tombuildsstuff, I assume the issue should be resolved when the importer/generator has been updated. Maybe we should keep this issue open, WDYT? |
Yeah agreed |
Is there an existing issue for this?
Community Note
Service Used
Migrate
API Versions Used
2020-01-01
Description
The response is paged with
nextLink
not in OData and sdk ignored it.References
Swagger: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/migrate/resource-manager/Microsoft.OffAzure/stable/2020-01-01/migrate.json#L3685
The text was updated successfully, but these errors were encountered: