[FEAT] Beta paginated_api_keys
function
#334
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
paginated_api_keys
toUser
to return a paginated list of API keys, rather than unpaginated fromapi_keys
NOTE: This beta function exists in the GA
User
class rather than in a separateBeta\User
class because this method is an instance method. It would only be accessible onBeta\User
objects, which wouldn't have any other of the existing functions that exist on theUser
object. They would either have to be entirely re-implemented or a converter betweenUser
andBeta\User
would have to be introduced; both strategies would add extra overhead and require changes to the end-user's workflow.More recent major versions of our library have effectively removed this issue by our re-architecture into services that make it easier to separate beta functions from GA functions. For now, a docstring has been added warning users that this new function is in beta.
Testing
Pull Request Type
Please select the option(s) that are relevant to this PR.