Project

General

Profile

Bug #2853

Charging error report changes

Added by Piyush Vijay 2 days ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Start date:
07/17/2026
Due date:
% Done:

0%

Estimated time:
Spent time:

Description

Charging error report changes

#1

Updated by Saransh Bakoliya 2 days ago

Today i have worked on ->
Analyzed the Charging Error Report drawer flow and investigated charger-based filtering behavior.
Integrated charger selection with the reporting APIs using the required chargerId parameter.
Validated charger dropdown data mapping from the reporting machines API.
Added dynamic charger selection state and applied charger filter handling.
Debugged duplicate API requests triggered during drawer initialization and filter updates.
Refactored the Apply filter flow to ensure filtering is controlled only through the Apply action.
Improved state management by separating selected filter values from applied filter values.
Fixed charger filter persistence across pagination and subsequent API requests.
Implemented dynamic summary state for charging error statistics received from the API.
Bound API summary response fields (totalSessions, failedCount, faultedCount, errorRate) to the UI.
Replaced static summary information with fully dynamic API-driven values.
Redesigned the charging error summary section to support multiple summary metrics.
Updated UI labels to display Error Rate instead of Fail Rate based on API response.
Performed end-to-end debugging of request payloads using browser Network tools and console logs.
Validated API request payloads for charger, station, date range, pagination, and export scenarios.
Reviewed and refined filter reset and initialization logic to maintain consistent report behavior.
Performed overall code cleanup, testing, and verification to ensure stable Charging Error Report functionality and accurate API integration.

Also available in: Atom PDF