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
Is your feature request related to a problem? Please describe.
I am always having issues with the count query param on the /api/v1/users.list api request, when I just want to get all of the existing users.
My intention is to get the full list of users and I don't want to just send a ridiculous integer number as a count (ex: 999 999 999).
Although the count param is useful for pagination, to not get the full list at once, when I really want to get the full list, I would really like another way of doing it.
Describe the solution you'd like
I would really like for the /api/v1/users.list api to have an extra param supported, that let's the developer specify if it just wants the full list of the users, like a boolean.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am always having issues with the count query param on the /api/v1/users.list api request, when I just want to get all of the existing users.
My intention is to get the full list of users and I don't want to just send a ridiculous integer number as a count (ex: 999 999 999).
Although the count param is useful for pagination, to not get the full list at once, when I really want to get the full list, I would really like another way of doing it.
Describe the solution you'd like
I would really like for the /api/v1/users.list api to have an extra param supported, that let's the developer specify if it just wants the full list of the users, like a boolean.
The text was updated successfully, but these errors were encountered: