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
Status for commands was originally added to this module based on
my experience with other REST API's where individual commands could
easily take 10-20 seconds.
Practical usage has shown that most GitHub requests in reality take
under one second. The additional work that PowerShell has to do in
order to display progress to the user can easily make the overall
command take 4-6 times longer than its actual execution time.
Therefore, status is being ripped out of this module (for the most
part). `Invoke-GHRestMethod` and `Invoke-SendTelemetryEvent` no
longer have bifurcating execution paths based on the value of
`$NoStatus`. Everything runs synchronously now on the command prompt.
* `DefaultNoStatus` has been deprecated. Its value will be ignored.
* The `NoStatus` switch has not been removed from the module commands
in order to avoid a breaking change. It may be removed in a future
update.
* `Invoke-GHRestMethod -ExtendedResult` has been updated to include
the next page's number and the total number of pages for the
REST request.
* A new configuration value has been added: `MultiRequestProgressThreshold`
`Invoke-GHRestMethodMultipleResult` will display a ProgressBar to the
user tracking the number of remaining requests for the overall
execution of the requested command based on this threshold value. It
will only display the progress bar if the number of requets needed
meets or exceeds this threshold value. This defaults to 10, and can
be disabled with a value of 0. Practical usage has shown that this
adds less than a second of additional time to the overall execution
of a multi-request command (quite different than the previous status).
* `Wait-JobWithAnimation` has been removed since it's no longer used.
Fixes#247
0 commit comments