Advanced User Management

[pdrivom]

Is your feature request related to a problem? Please describe.
It would be really nice to have a complete paginated CRUD management of Users, Roles, Groups, Permissions with the option to search.

Describe the solution you'd like
Possibility to create User with Roles/Groups with a set of Permissions, all previously created.

Describe alternatives you've considered
User can be created with a 'default' Role/Group but can be edited later on.

[seapagan]

@pdrivom

I've included only minimal role management at this time, deliberately. For a simple API, this is all that is needed. As I nail down the API structure, I will definitely integrate a more granular (and configurable) roles and groups system. The whole User system needs tidying before then, which is on my TODO list.

I have planned pagination as a feature to be added (I was thinking about this yesterday). However, I'm not sure about this comment on the library you linked:

Please, be careful when you work with databases, because default paginate will require to load all data in memory.

I have written pagination strategies from scratch in several languages, and it should only load the chunk being paginated (SQL has this functionality hard-coded into it) and then get the next chunk on demand. I may have misread it?

[pdrivom]

Hey @seapagan, my "requests" are basically enhancements as soon as the template gets stronger.

For a big user base application the paginated responses and the ability to quick search on server side is a great feature.

This pagination lib is not by far mandatory, the pagination itself is done on database query level and just needs something to wrap that data and return back to client the page number/size/etc and the next page url request.

[seapagan]

Hey @seapagan, my "requests" are basically enhancements as soon as the template gets stronger.

For sure, and I really appreciate them 😃. I have also enabled the 'Discussions' on this Repo, so that is a good place for ideas and brainstorming.

For a big user base application the paginated responses and the ability to quick search on server side is a great feature.

Utterly. I wrote a backend that served UPRN info for the whole of Scotland. Pagination was a 100% requirement for that. Also similar problems with searching large datasets which is where Postgresl tsvector and proper indexing come in.

This pagination lib is not by far mandatory, the pagination itself is done on database query level and just needs something to wrap that data and return back to client the page number/size/etc and the next page url request.

Yeah, I've done a bit of pagination before and would probably prefer to write a turnkey solution for the pagination. Its definitely in the plan!