zwave-js / zwave-js-ui / 19503417644

20%

push

github

feat: add completion status messages for task operations (#4465)

Status indicators showed progress percentages without clear completion
messages, leaving users uncertain whether operations finished
successfully or stalled at 100%.

## Changes

**Modified `api/lib/ZwaveClient.ts`:**

- Added completion status to `backupNVMRaw()` after successful NVM
backup
- Added completion status to `restoreNVM()` after successful NVM restore
- Updated `_onRebuildRoutesProgress()` to show "COMPLETED" status when
all nodes are healed

All changes use the existing `_updateControllerStatus()` pattern for
consistency.

## Before/After

**NVM Backup:**
- Before: `Backup NVM progress: 100%` (ambiguous)
- After: `NVM backup completed successfully` (clear)

**NVM Restore:**
- Before: `Restore NVM progress: 100%` (ambiguous)
- After: `NVM restore completed successfully` (clear)

**Rebuild Routes:**
- Before: `Rebuild Routes process IN PROGRESS. Healed 100 nodes` (even
when complete)
- After: `Rebuild Routes process COMPLETED. Healed 100 nodes` (when
finished)

> [!WARNING]
>





<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
>
<__filter_complete__></__filter_complete__></details><issue_title>feat:
update status on task completion</issue_title>
><issue_description>**Is your feature request related to a problem?
Please describe.**
> It can be confusing when the status indicator shows a message that is
really old and doesn't obviously pertain to completion.
> 
> **Describe the solution you'd like**
> Completion messages should be triggered when tasks that create other
status messages finish.
> 
> **Describe alternatives you've considered**
> The only obvious alternative is user education, which must be repeated
with new users.
> 
> **Additional context**
> My ZUI currently shows "Backup NVM progress: 100%" in the status. This
doesn't make it clear whether the backup completed or got stuck.
Additi... (continued)

333 of 441 branches covered (75.51%)

Branch coverage included in aggregate %.

0 of 7 new or added lines in 1 file covered. (0.0%)

4048 of 21388 relevant lines covered (18.93%)

1.18 hits per line