Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@themylogin
Copy link
Contributor

Changes:

This event was renamed in the middleware: truenas/middleware#17581

Testing:

Downstream

Affects Reasoning
Documentation
Testing

@themylogin themylogin requested a review from a team as a code owner November 10, 2025 13:55
@themylogin themylogin requested review from a team and aervin and removed request for a team November 10, 2025 13:55
@bugclerk bugclerk changed the title Rename zfs.pool.scan to pool.scan NAS-138409 / 26.04 / Rename zfs.pool.scan to pool.scan Nov 10, 2025
@bugclerk
Copy link
Contributor

@claude
Copy link

claude bot commented Nov 10, 2025

Claude finished @themylogin's task —— View job


Review Complete ✅

Todo List

  • Read review guidelines
  • Examine all changed files
  • Search for any remaining references to zfs.pool.scan
  • Check for test files that need updates
  • Provide comprehensive review feedback

Review Feedback

The changes look clean and straightforward! 🎯 The renaming from zfs.pool.scan to pool.scan has been consistently applied across all relevant files in the UI codebase.

What's working well:

  • All WebSocket event subscriptions have been updated correctly (api-event-directory.interface.ts:53, resilver-progress.component.ts:53, resilvering-indicator.component.ts:36, storage-health-card.component.ts:171)
  • No remaining references to the old zfs.pool.scan event name in the codebase
  • Test files don't need updates since they mock the API service generically without hardcoding event names
  • The change is minimal and focused, reducing the risk of introducing bugs

Observations:
The widget-storage.component.ts file also uses pool.scan, but that's accessing the scan property from the Pool interface (line 267), not the WebSocket event, so it's correctly unchanged.

No issues found - this PR is ready to merge! 🚀

Copy link
Contributor

@AlexKarpov98 AlexKarpov98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@codecov
Copy link

codecov bot commented Nov 10, 2025

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 86.28%. Comparing base (7c5e6f5) to head (213d23f).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
...r/resilver-progress/resilver-progress.component.ts 0.00% 1 Missing ⚠️

❌ Your patch check has failed because the patch coverage (66.66%) is below the target coverage (75.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #12792   +/-   ##
=======================================
  Coverage   86.28%   86.28%           
=======================================
  Files        1825     1825           
  Lines       67908    67908           
  Branches     8219     8219           
=======================================
  Hits        58595    58595           
  Misses       9313     9313           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@themylogin themylogin merged commit 55e8798 into master Nov 10, 2025
11 of 12 checks passed
@themylogin themylogin deleted the NAS-138409 branch November 10, 2025 14:11
@bugclerk
Copy link
Contributor

JIRA ticket https://ixsystems.atlassian.net/browse/NAS-138409 is targeted to the following versions which have not received their corresponding PRs: 25.10.1

@bugclerk
Copy link
Contributor

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.

@truenas truenas locked as resolved and limited conversation to collaborators Nov 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants