You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: