🌟🚀Feature/Invoke-GitHubRestMethod #294
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Invoke-GitHubRestMethod
Invoke-RestMethodinstead ofInvoke-WebRequestSupportsPaging(First and Skip, but not IncludeTotal)$GITHUB_RESPONSESglobal variable to store a collection of (Content, Date, Headers, StatusCode, and Uri) objects, because attempts to set a variable in the parent scope failed. I added anHttpResponsesVariableproperty to the config, so someone can opt for a different global variable name as a matter of preference or necessity in the event of a conflict.Accept, which should be specified via aHeaders.New .PARAMETERs
1and[int]::MaxValue.I reworked Get-GitHubUser using Invoke-GitHubRestMethod as a demonstration of the impact.
Type of change
Checklist