fix(ValidateForm): support formless

[ArgoZhang]

Link issues

fixes #8294

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

Bug Fixes:

• Prevent errors when ValidateForm is initialized with an ID that does not exist in the DOM, allowing use in formless contexts.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Guard ValidateForm initialization to safely handle cases where the target element does not exist, preventing errors when used without an associated form element ("formless" support).

File-Level Changes

Change	Details	Files
Make ValidateForm initialization resilient when the target element is missing, only binding events when a valid element is found and dissubmit is enabled.	Wrap element lookup and setup logic in a null-check to skip initialization when document.getElementById returns null. Retain existing data storage via Data.set and event binding via bind(el) but execute them only when the element exists. Preserve the dissubmit attribute check and conditional binding logic under the new guard.	src/BootstrapBlazor/Components/ValidateForm/ValidateForm.razor.js

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#8294	Prevent runtime errors in ValidateForm when used in formless mode (no associated DOM element), ensuring it safely handles the absence of the target element.	✅

Possibly linked issues

• bug(ValidateForm): Formless 模式下报错 #8294: The PR adds a null check in ValidateForm init to prevent errors in Formless mode, fixing 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

[bb-auto]

Auto approved by bb-auto

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider returning early when el is not found (e.g., if (!el) return;) to reduce nesting and keep the init function flatter and easier to read.
• If init failing to find an element indicates a misconfiguration, you may want to add a debug log or comment to make this silent failure more discoverable during development.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider returning early when `el` is not found (e.g., `if (!el) return;`) to reduce nesting and keep the `init` function flatter and easier to read.
- If `init` failing to find an element indicates a misconfiguration, you may want to add a debug log or comment to make this silent failure more discoverable during development.

---

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 (8939349) to head (80b8922).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #8295   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          769       769           
  Lines        34478     34478           
=========================================
  Hits         34478     34478           

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 Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.