Closed gabrielsroka closed 1 year ago
it looks like this was rolled back due to breaking tests. is there a plan to fix the tests?
Hi there! @gabrielsroka, thank you for your initial PR. Unfortunately, at this time, it is not on our roadmap to re-enable after finding it broke our tests. However, I have created an internal ticket to track this as a feature to re-enable in the future. We appreciate your feedback and will keep it in mind
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 https://github.com/okta/okta-sdk-python/issues/326#issuecomment-1314496367