feat(OfficeViewer): add OfficeViewer component

[ArgoZhang]

Link issues

fixes #6286

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

Add a new OfficeViewer sample page to showcase the OfficeDocumentViewer component, integrate it into the demo navigation, and update related samples and localization.

New Features:

• Introduce an OfficeViewer demo page with a Select dropdown and OfficeDocumentViewer component with load-toasting feedback
• Register a new "OfficeViewer" menu item in the demo navigation

Enhancements:

• Remove obsolete entries from the FileViewers sample file list
• Update the PdfViewers sample to use the correct PDF file path

Documentation:

• Add English and Chinese localization entries for OfficeViewer titles, descriptions, and toast messages
• Include OfficeViewer in the docs.json for sample documentation

[sourcery-ai]

Reviewer's Guide

This PR adds a new OfficeViewer component with its sample page, integrates it into the application menu and localization resources, updates project configurations, and refines existing file viewer samples.

Class diagram for the new OfficeViewers component

classDiagram
    class OfficeViewers {
        - List<SelectedItem> _docs
        - string _doc
        + Task OnLoaded()
    }
    class ToastService
    OfficeViewers --> ToastService : uses
    class SelectedItem
    OfficeViewers --> SelectedItem : contains list of

Loading

Class diagram for integration of OfficeDocumentViewer in sample page

classDiagram
    class OfficeDocumentViewer {
        +string Url
        +string Height
        +EventCallback OnLoaded
    }
    class OfficeViewers {
        - string _doc
        + Task OnLoaded()
    }
    OfficeViewers --> OfficeDocumentViewer : uses

Loading

File-Level Changes

Change	Details	Files
Introduce OfficeViewer sample component	Created OfficeViewers.razor sample page with routing and localization Implemented code-behind with ToastService injection and document selection list Defined OnLoaded callback to display success toast	src/BootstrapBlazor.Server/Components/Samples/OfficeViewers.razor src/BootstrapBlazor.Server/Components/Samples/OfficeViewers.razor.cs
Register OfficeViewer in application menus	Added new menu entry marked as new for OfficeViewer Set display text and URL for the new menu item	src/BootstrapBlazor.Server/Extensions/MenusLocalizerExtensions.cs
Include localized strings for OfficeViewer	Added English texts for titles, descriptions, and toast content Added Chinese translations for the new entries Updated documentation navigation entries	src/BootstrapBlazor.Server/Locales/en-US.json src/BootstrapBlazor.Server/Locales/zh-CN.json src/BootstrapBlazor.Server/docs.json
Cleanup and update existing sample file viewers	Removed unused sample files from FileViewers example Corrected PDF sample file path in PdfViewers example	src/BootstrapBlazor.Server/Components/Samples/FileViewers.razor.cs src/BootstrapBlazor.Server/Components/Samples/PdfViewers.razor
Update project configurations	Added package reference for OfficeDocumentViewer Updated server and core project files to include new dependencies	src/BootstrapBlazor.Server/BootstrapBlazor.Server.csproj src/BootstrapBlazor/BootstrapBlazor.csproj

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6286	Add an OfficeViewer component to the application.	✅

---

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!

---

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 (547980d) to head (e0047c5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6287   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          712       712           
  Lines        31397     31397           
  Branches      4437      4437           
=========================================
  Hits         31397     31397           

Flag	Coverage Δ
BB	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.