Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: reusable and accessible table component #1700

Merged
merged 37 commits into from
Sep 5, 2022
Merged

Conversation

flea89
Copy link
Contributor

@flea89 flea89 commented Aug 3, 2022

Resolves #1711
Relates to bigger ticket #1362
In this PR we created a Table component that is accessible and reusable

joshJarr and others added 30 commits May 27, 2022 15:33
…ination. Add removed `after` filtering parameter to the endpoint. Document `sortBy`, `sortOrder`, `after` & `offset` in the swagger docs. Set `Size` param default to 10 from 25.
…size is returned. Add tests for date filtering (before & after) and sorting by date.
…se for get user/uploads to allow for pagination. Renames `Link` to `Next_link` in header to be more descriptive.
…o prevent comparing to message string. Remove .only.
…optimise `sortBy` queries on the `GET user/uploads` endpoint.
@flea89 flea89 changed the title Feat: reusable and accessible table component feat: reusable and accessible table component Aug 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Aug 4, 2022

@flea89
Copy link
Contributor Author

flea89 commented Aug 8, 2022

@joshJarr, while working on #1699 I've actually changed some more table stuff in there, but hopefully nothing fundamentally different from what you see here.

@flea89 flea89 merged commit a4643a0 into main Sep 5, 2022
@flea89 flea89 deleted the feat/table-component branch September 5, 2022 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New table component: reusable, accessible and api pagination compliant
2 participants