LCFS - Create backend 'End Use' table for compliance reporting calculation (*Not sure if needed)
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 87
Description
**Description:**
Develop a new AG Grid table for the 'Compliance reporting' calculation page titled 'End Use'. This page should be accessible to only IDIR users. The table should include the following columns, arranged from left to right: Fuel type, End use.
The default sorting of the table should be by year in descending order. Ensure that the column widths are adequately formatted to display information clearly. Implement searchable filters for columns. The table should be server-side to optimize performance.
**Purpose and Benefit to User:**
This feature enables users to view and update the components needed for calculating compliance units.
**Acceptance Criteria:**
- [ ] Given I am a , When I am , then
- [ ] Given I am a , When I am , then
**Development Checklist:**
- [ ] A
- [ ] B
- [ ] C
**Notes:**
This is setting up for a future feature that will allow IDIR access to edit the figures in these tables similar to the fuel code feature by using AG Grid.
Contributor guide
Research direction
Start at the Compliance reporting calculation page and inspect the existing fuel code AG Grid implementation referenced in the notes. Confirm the IDIR-only access path, server-side data flow, sorting and searchable columns before defining the missing files and tests; done means the End Use table shows Fuel type and End use with the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100