test(Upload): improve code coverage

[ArgoZhang]

Link issues

fixes #6167

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Refactor the file format icon logic in UploadPreviewList to streamline filename retrieval and guard against empty extensions.

Enhancements:

• Use GetFileName() to consistently obtain the filename instead of manually checking OriginFileName and FileName
• Only resolve the icon and add the CSS class when the file extension is non-empty
• Change GetFileExtensions to accept a non-nullable string parameter for stricter extension handling

[sourcery-ai]

Reviewer's Guide

Refactors UploadPreviewList component to improve file icon resolution by centralizing extension retrieval from the file object, consolidating icon mapping logic within the non-null extension guard, and tightening method signatures for null-safety.

Updated Class Diagram for Upload Components

classDiagram
    class UploadPreviewList {
        -GetFileFormatClassString(item: UploadFile) : string?
        -GetFileExtensions(fileExtension: string) : string?
    }
    class UploadFile {
        +GetFileName() : string
        +OriginFileName : string?
        +FileName : string
    }
    UploadPreviewList ..> UploadFile : uses

Loading

File-Level Changes

Change	Details	Files
Centralize file extension retrieval and icon mapping in GetFileFormatClassString	Use item.GetFileName() instead of OriginFileName/FileName coalescing Move icon lookup and AddClass call inside non-null extension block Remove duplicated icon builder.AddClass call outside the block	src/BootstrapBlazor/Components/Upload/UploadPreviewList.razor.cs
Strengthen GetFileExtensions signature for null-safety	Change parameter from nullable string? to non-nullable string Ensure fileExtension passed is always non-null before calling	src/BootstrapBlazor/Components/Upload/UploadPreviewList.razor.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6167	Improve code coverage for the Upload component.	✅

Possibly linked issues

• test(Upload): improve code coverage #6167: PR has same title as issue and links it, refactoring code in the Upload component.
• test(Upload): improve code coverage #6167: PR fixes issue 6167 by modifying how file extensions are handled in the Upload component.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ArgoZhang - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (d139e8c) to head (7209371).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main     #6168   +/-   ##
========================================
  Coverage   99.99%   100.00%           
========================================
  Files         704       704           
  Lines       31099     31099           
  Branches     4395      4394    -1     
========================================
+ Hits        31098     31099    +1     
+ Partials        1         0    -1     

Flag	Coverage Δ
BB	100.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.