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

[TA] Delete custom HealthStatusNextPageAsync for in health pagination #19183

Merged
merged 2 commits into from
Mar 5, 2021

Conversation

maririos
Copy link
Member

@maririos maririos commented Mar 3, 2021

Part of: #18373
Currently I manually wrote HealthStatusNextPageAsync and HealthStatusNextPage functions in order to have pagination in Health because we were not getting them from the swagger or codegen. This change is doing transformations in order to generate it automatically so we can delete my manual code.

Two action items I am still working on:

  • Work with the service to understand why the nextlink doesn't include the showStats (they have opened an issue)
  • See if we can add pagination to the swagger so the transform is no longer needed

In a future PR I will do the same for Analyze endpoint

/// <param name="showStats"> (Optional) if set to true, response will contain request and document level statistics. </param>
/// <param name="cancellationToken"> The cancellation token to use. </param>
/// <exception cref="ArgumentNullException"> <paramref name="nextLink"/> is null. </exception>
public async Task<Response<HealthcareJobState>> HealthStatusNextPageNextPageAsync(string nextLink, bool? showStats = null, CancellationToken cancellationToken = default)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is created twice and it has already been reported: Azure/autorest.csharp#1056
I made the name very very ugly so no one uses it :P

@maririos maririos merged commit 886e90f into Azure:master Mar 5, 2021
@maririos maririos deleted the pagination branch March 9, 2021 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants