refactor(SvgEditor): use HeadContent render static assets

[ArgoZhang]

use HeadContent render static assets

Summary of the changes (Less than 80 chars)

Description

fixes #181

Customer Impact

Regression?

• Yes
• No

[If yes, specify the version the behavior has regressed from]

Risk

• High
• Medium
• Low

[Justify the selection above]

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

Enhancements:

• Refactor SvgEditor component to use HeadContent for rendering static assets.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR refactors the SvgEditor component to use HeadContent for rendering static assets, specifically CSS files. The implementation moves away from dynamic JS-based CSS loading to a more standard approach using Blazor's HeadContent component, while also consolidating CSS imports and fixing some path references.

Sequence diagram for SvgEditor initialization

sequenceDiagram
    participant User
    participant SvgEditor
    participant HeadContent
    User ->> SvgEditor: init(id, options)
    SvgEditor ->> HeadContent: Add link to CSS
    HeadContent -->> SvgEditor: CSS loaded
    SvgEditor -->> User: Editor initialized

Loading

Class diagram for SvgEditor component refactor

classDiagram
    class SvgEditor {
        +init(id, options)
    }
    class HeadContent {
        +link(rel, href)
    }
    SvgEditor --> HeadContent : uses
    note for SvgEditor "Refactored to use HeadContent for static assets"

Loading

File-Level Changes

Change	Details	Files
Changed the way CSS assets are loaded in the SVG editor	Removed dynamic CSS loading through JavaScript utility function Added HeadContent component to load CSS statically Consolidated CSS files into a bundle Fixed extension path to use relative URL	src/components/BootstrapBlazor.SVGEditor/Components/SvgEditor/SvgEditor.razor.js src/components/BootstrapBlazor.SVGEditor/Components/SvgEditor/SvgEditor.razor
Relocated and restructured CSS files	Moved component-specific CSS to a bundled file Added CSS import statement to include editor styles Maintained existing SVG editor styling rules	src/components/BootstrapBlazor.SVGEditor/Components/SvgEditor/SvgEditor.razor.css src/components/BootstrapBlazor.SVGEditor/wwwroot/svgedit.bundle.css

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#181	Use HeadContent to render static assets (CSS) instead of dynamic JavaScript-based asset loading	✅

Possibly linked issues

• refactor(SvgEditor): use HeadContent render static assets #181: The PR implements the solution described in the issue by using HeadContent to render static assets.

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.}