v3 users

[krismarc]

Hi @antechrestos

is there any reason for not having v3 users in this client? I believe adding it is rather straightforward.

Would you mind adding it? If you have no time I could try to raise PR that would support it.

Best regards,
K.M.

[antechrestos]

@krismarc I've made a small implementation, tell me whether it is ok.

[krismarc]

That was quick. Actually, I was mainly looking for listing options. Thanks for considering and adding other methods!
I'll try to test tomorrow or day after tomorrow.

One remark so far: you might update the list of available managers in the readme.

I'd be also interested in other managers 😃

routes
droplets
packages
audit events
organization quotas
stacks

..sorted by the importance for me. Just their class declarations which abstract EntityManager class, extra api methods implementations is something we can pick later in the future if there's a need.

I believe having all possible classes declared which abstract EntityManagers for most of api resources would be perfect.
It would provide lots of possibilities with rather low effort as it's all coming out of the box from what you have already implemented.

What do you think? 😄

[antechrestos]

@krismarc what do you mean by

That was quick. Actually, I was mainly looking for listing options. Thanks for considering and adding other methods!

you mean being able to filter it as specified in list users operation ?

For other managers, would you mind create a dedicated issue?

thanks

[krismarc]

I mean, create, update and delete methods in UserManager class. All I need now is EntityManager abstraction for missing resources so I can get pagination and listing option available.

I've created an issue: #280

[antechrestos]

Ok so for now each entity manager expose a generic list that allows filtering

[antechrestos]

I will merge the PR and let you make return if needed