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.
currently, pagination requires many lines of code:
my 2 line PR would reduce some of the boilerplate code (the last line above ^^^) to:
it'd be even nicer to have an
async
generator to either return each page, or each object in the page (eg, Users). basically take the 5 lines above and move them into the SDK itself. then useasync for
to get the users:this is more Pythonic, and similar to how other Okta SDKs work, eg, Node.js (https://github.com/okta/okta-sdk-nodejs#serial-or-parallel-synchronous-work), and I think Java, too, but I can't tell from the example.
Node.js example https://github.com/okta/okta-sdk-nodejs#list-all-org-users
my code doesn't handle errors, but it could. error handling should use
try
--it's more Pythonic.see also #326 (comment)