doc(Display): update xml documentation

[ArgoZhang]

Link issues

fixes #7625

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

Documentation:

• Refine XML documentation on Display component lookup properties to inherit comments from the corresponding ILookup members.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refines XML documentation inheritance for Display lookup-related parameters by specifying explicit ILookup member references, improving documentation clarity without changing runtime behavior.

File-Level Changes

Change	Details	Files
Clarify XML documentation for lookup-related parameters in Display by using explicit cref targets to ILookup members.	Replaced bare tags on lookup-related properties with , , , , and . Ensured that Display’s public API documentation is explicitly tied to the corresponding ILookup interface members, improving generated docs and IDE tooltips.	src/BootstrapBlazor/Components/Display/Display.razor.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#7625	Update the XML documentation for the Display component to clearly indicate which ILookup interface members each parameter/property is inheriting documentation from.	✅

Possibly linked issues

• doc(Display): update xml documentation #7625: The PR directly updates Display component XML docs with explicit ILookup cref tags, matching the issue request.

---

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 - 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 (4b2f98c) to head (672b28b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #7626   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          749       749           
  Lines        33017     33017           
  Branches      4581      4581           
=========================================
  Hits         33017     33017           

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

[Copilot]

Pull request overview

This PR updates the XML documentation for the Display component to explicitly reference ILookup interface members using the cref attribute in inheritdoc tags. This improves documentation clarity by making it explicit which interface member is being documented.

Changes:

• Updated five ILookup interface property documentation tags from <inheritdoc/> to <inheritdoc cref="ILookup.PropertyName"/>

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.