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

Enable paging in command results #1251

Closed
troydai opened this issue Nov 4, 2016 · 5 comments
Closed

Enable paging in command results #1251

troydai opened this issue Nov 4, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@troydai
Copy link
Contributor

troydai commented Nov 4, 2016

Today, for commands which produce large amount of result data and take long time to execute the user experience is poor. The command doesn't provide feedback to indicate progress. The final output can be huge and inconvenient to consume if it is not captured in file.

Many REST API our commands depend on actually provide server side and/or client side paging. By leveraging the paging feature, we can provide a friendlier user interaction. If user opt in, the command can print result piece by piece as each page arrives.

The goal of this task is to design and implement such a mechanism in the core of the CLI so that most of the commands can be equipped with paging feature without changes to the commands themselves as long as the underlying Azure API supports paging.

@troydai
Copy link
Contributor Author

troydai commented Nov 4, 2016

Per discussion with @johanste I'll looking into this one.

@troydai troydai self-assigned this Nov 4, 2016
@troydai
Copy link
Contributor Author

troydai commented Jan 24, 2017

#1832

@tjprescott
Copy link
Member

How does this differ from #3481?

@troydai
Copy link
Contributor Author

troydai commented Jun 5, 2017

No.

@troydai
Copy link
Contributor Author

troydai commented Jun 5, 2017

Let me close this one as dup...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants