finos
Implement search, pagination, filtering and ordering in UI
Is your feature request related to a problem? Please describe.
Currently, all tables are presented in the UI without any form of search, pagination, filtering or ordering capability. This makes it very difficult to find items in the UI and makes it a pain to use.
Describe the solution you'd like
Each of the following views should be updated to include all of search, pagination, filtering and ordering:
- [ ] Repositories
- [ ] Dashboard
- [ ] Users
Ideally this should be implemented as a component that can be written once and applied multiple times to our different data sources, i.e. repositories, users. It also helps with future proofing as we will soon be introducing more data constructs like licenses (#604).
This task is well suited to anyone who loves a bit of frontend design 🖌️ 🎨 Also happy to support and work with anyone on this issue too who wants to try their hand at something new ❤️
Hey @JamieSlome, I would like to work on this issue. just wanted to confirm if it's currently assigned to anyone else? Also, is there a deadline or timeline set for completing this task?
@tarnveerSingh - absolutely! No deadline 👍
I will assign the ticket to you. Thank you for offering your support and looking forward to your pull request!
@tarnveerSingh, @tt-gideonaryeetey has offered to take this one on and to start the implementation. Shall we find you another issue to work on? 👍
@tarnveerSingh - thoughts on https://github.com/finos/git-proxy/issues/627?
@JamieSlome I won't be able to work on it atm, but I'll definitely keep an eye out for any developments or opportunities to contribute later.
Hi @JamieSlome , I am participating in the Citi Hackathon. Can I take up this issue?
hi @JamieSlome , i have added pagination and search component and implemented it in Users and Repositories page as of now , tested it using dummy data as the original data contains info of only one repository and one user.
@darkhorse-420
Instead of dummy data in code update/add entries as much you want in in-memory database. Update repos.db and user.db to test your new component change. I was able to bring up multiple repos like this. Note: Keep "_id" unique for each entry.
Also, let me know if you need any help I am interested in contributing.
@JamieSlome Can you add me as an assignee, I would like to contribute here along with @darkhorse-420
