[ArgoZhang]

Link issues

fixes #1213

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

Support fingerprinted PDF viewer CSS assets across supported .NET versions.

Bug Fixes:

• Ensure the PDF viewer stylesheet is loaded correctly when static assets use fingerprinted URLs.

Build:

• Update PdfViewer packaging configuration to support the fingerprinted CSS asset.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PDF viewer now loads its CSS through a URL supplied by the component, using .NET 9+ asset-manifest resolution for fingerprinted assets and preserving the legacy path for earlier targets.

Sequence diagram for fingerprinted PDF viewer CSS loading

sequenceDiagram
    participant PdfViewer as PdfViewer component
    participant JS as PdfViewer.razor.js
    participant Assets as .NET 9 asset manifest
    participant Browser as Browser

    PdfViewer->>PdfViewer: OnAfterRenderAsync(firstRender)
    alt .NET 9 or later
        PdfViewer->>Assets: Resolve Assets[StylePath]
        Assets-->>PdfViewer: Fingerprinted styleUrl
    else Earlier target
        PdfViewer->>PdfViewer: Use StylePath
    end
    PdfViewer->>JS: init(id, invoke, options, styleUrl)
    JS->>Browser: addLink(styleUrl)
    Browser-->>JS: Load pdf-viewer.css

Loading

File-Level Changes

Change	Details	Files
Pass a framework-resolved CSS asset URL into the PDF viewer initialization so the stylesheet can be fingerprinted on newer .NET versions while retaining the existing static path elsewhere.	Define the shared PDF viewer stylesheet path and resolve it through the asset manifest on .NET 9+. Extend JavaScript initialization to accept the resolved stylesheet URL and load it through the existing link helper. Update the component project configuration to support the asset fingerprinting setup.	src/components/BootstrapBlazor.PdfViewer/BootstrapBlazor.PdfViewer.csproj src/components/BootstrapBlazor.PdfViewer/PdfViewer.razor.cs src/components/BootstrapBlazor.PdfViewer/PdfViewer.razor.js

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1213	Load the PDF viewer CSS using a fingerprinted asset URL so browsers can cache it safely across updates.	✅

Possibly linked issues

• feat(PdfViewer): fingerprint CSS asset #1213: The PR resolves the issue by passing the framework-generated fingerprinted CSS URL to PdfViewer initialization.
• feat(PdfViewer): fingerprint CSS asset #1213: The PR supplies a fingerprinted CSS URL to PdfViewer initialization, matching the issue’s request to fingerprint the PDF CSS asset.
• feat(PdfViewer): fingerprint CSS asset #1213: The PR passes the fingerprinted CSS asset URL to JavaScript for loading, directly implementing the issue.

---

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.

[bb-auto]

Auto approved by bb-auto

[sourcery-ai]

Hey - 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