Skip to content

doc(Driver): update documentation - #1072

Merged
ArgoZhang merged 1 commit into
masterfrom
doc-driver
Jul 15, 2026
Merged

doc(Driver): update documentation#1072
ArgoZhang merged 1 commit into
masterfrom
doc-driver

Conversation

@ArgoZhang

@ArgoZhang ArgoZhang commented Jul 15, 2026

Copy link
Copy Markdown
Member

Link issues

fixes #1071

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

Improve inline and XML documentation for DriverJs-related components and models, providing clearer bilingual descriptions of properties, callbacks, and defaults without changing runtime behavior.

Enhancements:

  • Refresh DriverJs component, configuration, and popover XML comments with clearer English descriptions and Chinese translations to improve API documentation clarity.

Documentation:

  • Improve inline documentation for DriverJs configuration, steps, and popover APIs with bilingual XML summaries and default value explanations.

@bb-auto bb-auto Bot added the documentation Improvements or additions to documentation label Jul 15, 2026
@bb-auto bb-auto Bot added this to the v10.0.0 milestone Jul 15, 2026
@sourcery-ai

sourcery-ai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Reviewer's Guide

Updates DriverJs-related documentation comments to be bilingual (Chinese and English), clarifies default values and behaviors, and aligns naming with DriverJs instead of FocusGuide across configuration, component, popover, and step classes.

File-Level Changes

Change Details Files
Enrich XML documentation in the DriverJsConfig configuration class with bilingual summaries and explicit default values and behavior descriptions.
  • Replace single-language XML summaries with and sections for all public properties.
  • Document default values and semantics for animation, overlay, scrolling, keyboard control, interaction disabling, buttons, progress display, and callbacks.
  • Clarify callback properties for destroy lifecycle and overlay clicking, including behavior and purpose.
src/components/BootstrapBlazor.DriverJs/Components/DriverJsConfig.cs
Enhance documentation for the DriverJs component methods and parameters to describe tour control behavior in both Chinese and English.
  • Update class summary to describe DriverJs as a component instead of FocusGuide.
  • Add bilingual documentation for parameters (AutoDrive, Config, ChildContent) and JS-interoperable callbacks.
  • Add bilingual descriptions for all tour control methods (start, navigation, query methods, destroy, refresh, highlight, add/remove steps).
src/components/BootstrapBlazor.DriverJs/Components/DriverJs.razor.cs
Update DriverJsPopover and IDriverJsPopover documentation to clearly describe popover configuration options and button/progress behavior in two languages.
  • Add bilingual summaries for the popover configuration class and interface.
  • Document semantics and allowed values for position, alignment, buttons, progress text, and custom classes.
  • Ensure parameter and interface property comments are aligned and consistently describe defaults and accepted values.
src/components/BootstrapBlazor.DriverJs/Components/DriverJsPopover.cs
src/components/BootstrapBlazor.DriverJs/Components/IDriverJsPopover.cs
Improve documentation for DriverJsStep and highlight popover model to clarify step configuration and relationships to popover.
  • Add bilingual comments for step selector, title, description, skip behavior, and child content.
  • Document UpdatePopover behavior with bilingual description referencing FocusGuidePopover instance updates.
  • Add bilingual summary for DriverJsHighlightPopover describing it as a highlight popover configuration class.
src/components/BootstrapBlazor.DriverJs/Components/DriverJsStep.cs
src/components/BootstrapBlazor.DriverJs/Models/DriverJsHighlightPopover.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#1071 Update and improve the DriverJs-related component documentation/comments (e.g., XML summaries and property descriptions) to be clearer and more complete.
#1071 Align documentation terminology by updating references from FocusGuide/IGuidePopover to DriverJs/IDriverJsPopover where appropriate.

Possibly linked issues


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

@bb-auto bb-auto Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved by bb-auto

@ArgoZhang
ArgoZhang merged commit a67b794 into master Jul 15, 2026
3 checks passed
@ArgoZhang
ArgoZhang deleted the doc-driver branch July 15, 2026 08:41

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue, and left some high level feedback:

  • The XML comments for OverlayClickBehavior are a bit unclear (“close nextStep function”); consider rephrasing to explicitly describe the supported values and their effect, e.g. "close" to end the tour, "next" to advance to the next step.
  • Several properties now document specific default values (e.g., ShowProgress, ShowButtons, ProgressText) but are nullable and not initialized; double‑check that the described defaults match the actual runtime defaults applied by DriverJs or your wrapper and adjust the comments if needed.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The XML comments for `OverlayClickBehavior` are a bit unclear (“close nextStep function”); consider rephrasing to explicitly describe the supported values and their effect, e.g. `"close" to end the tour, "next" to advance to the next step`.
- Several properties now document specific default values (e.g., `ShowProgress`, `ShowButtons`, `ProgressText`) but are nullable and not initialized; double‑check that the described defaults match the actual runtime defaults applied by DriverJs or your wrapper and adjust the comments if needed.

## Individual Comments

### Comment 1
<location path="src/components/BootstrapBlazor.DriverJs/Components/DriverJsPopover.cs" line_range="79-80" />
<code_context>

     /// <summary>
-    /// Whether to show the progress text in popover. (default true)
+    /// <para lang="zh">获得/设置 是否在弹窗中显示进度文本,默认为 true</para>
+    /// <para lang="en">Gets or sets whether to show the progress text in popover. Default is true</para>
     /// </summary>
     [Parameter]
</code_context>
<issue_to_address>
**question (bug_risk):** The documented default for `ShowProgress` in the popover may not match the actual runtime default behavior.

`ShowProgress` is declared as `bool?` without an initializer, so its CLR default is `null`, not `true`. Please confirm how `null` is handled at runtime (e.g., treated as `true`) and update the wording to describe the “unset” behavior precisely, or set an explicit default value if it should always be `true`.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +79 to +80
/// <para lang="zh">获得/设置 是否在弹窗中显示进度文本,默认为 true</para>
/// <para lang="en">Gets or sets whether to show the progress text in popover. Default is true</para>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question (bug_risk): The documented default for ShowProgress in the popover may not match the actual runtime default behavior.

ShowProgress is declared as bool? without an initializer, so its CLR default is null, not true. Please confirm how null is handled at runtime (e.g., treated as true) and update the wording to describe the “unset” behavior precisely, or set an explicit default value if it should always be true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

doc(Driver): update documentation

1 participant