Auth Web - Add dissolution batch history grid(exclude column filtering)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Create initial dissolution batch history grid as per [designs](https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution-%26-Delay-of-Dissolution?node-id=1115-1404&t=2YmOJ1Zs63J7mdGr-0).
The grid should be able pull back data and support paging and sorting via the GET /admin/batches endpoint. Reference #22618 for implementation details for the endpoint.
The filtering columns can be excluded in this ticket unless it’s fairly effortless to include.
**TODOs**
- [ ] Create dissolution batch history grid in Auth Web
- [ ] Grid retrieves data from GET /admin/batches endpoint
- [ ] Grid supports paging
- [ ] Grid supports sorting by column name
- [ ] Grid supports sort order
- [ ] Add/update tests as appropriate
**GET /admin/batches endpoint URL structure**
```
GET /api/v2/admin/batches?page=1&page_size=2&sort_by=&sort_order=desc
```
**Sample response from GET /admin/batches endpoint**
Note that we will be returning all columns in the `batches` table. It will be up to the UI to decide which columns to use.
```json
{
"batches": [
{
"id": 1,
"created_date": "2024-06-25",
"end_date": "2024-08-26",
"status": "COMPLETED",
"size": 344,
"max_size": 600,
"batch_type": "DAILY",
"notes": null
},
{
"id": 15,
"created_date": "2024-06-19",
"end_date": null,
"status": "FAILED",
"size": 300,
"max_size": 600,
"batch_type": "DAILY",
"notes": "reason for failure"
}
],
"total": 10,
"pages": 5,
"current_page": 1
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in Auth Web by following the dissolution batch history design and the existing implementation details in issue #22618. Use GET /admin/batches with its pagination and sorting parameters, and add or update tests as appropriate. Done means the grid displays the selected batch columns, retrieves data, pages through results, and sorts by column and order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100