LCFS - Compliance report fuel supply input AG grid table reorganizes when auto-save happens
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 87
Description
**Describe the task**
Prevent the fuel supply input line from reorganizing after the initial save. Currently, when a user inputs a new fuel supply line at the bottom of the grid, the auto-save function triggers, and the input line gets moved to the top of the table. The desired functionality is for the table to maintain the order in which the fuel suppliers enter their data, even after the auto-save occurs.
**Purpose**
This task is essential to enhance the user experience by preserving the order of entries as input by fuel suppliers. It avoids confusion caused by unexpected reorganization and ensures data remains in the user's preferred sequence, thereby improving usability and efficiency in data entry processes.
**Acceptance Criteria**
- [ ] After the initial input of a fuel supply line, the line should remain in its original position within the table/grid.
- [ ] The auto-save function should not cause any reorganization of the fuel supply lines.
- [ ] The order of fuel supply lines should reflect the sequence in which they were added by the user.
- [ ] Proper testing is conducted to ensure no other functionalities are affected by this change.
**Additional context**
- Investigate the auto-save functionality to determine why it triggers a reorganization of the input lines.
- Ensure that any sort or filter functions applied by the user will work independently of this task and maintain their functionality.
Contributor guide
Research direction
Start by tracing the fuel supply input grid and its auto-save functionality to identify where the table order changes after the initial save. Verify the behavior by adding a new fuel supply line at the bottom, triggering auto-save, and confirming that the line remains in place without affecting sorting or filtering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100