Enhance HyperLink component documentation and optimize CI workflows

[Copilot]

The HyperLink component documentation only listed 3 core properties without implementation details, styling capabilities, or usage guidance. Additionally, GitHub Actions workflows were running unnecessary builds and tests for documentation-only changes.

Changes

Documented Supported Features

• Core properties: Added ToolTip (was undocumented)
• Styling: BackColor, ForeColor, BorderColor, BorderStyle, BorderWidth, CssClass, Height, Width
• Font styling: Bold, Italic, Names, Overline, Size, Strikeout, Underline
• Visibility: Visible property
• Lifecycle events: OnDataBinding, OnInit, OnLoad, OnPreRender, OnUnload, OnDisposed

Added Unsupported Features Section

Clarified which Web Forms properties exist but don't work:

• Enabled - exists for compatibility, doesn't disable the link
• TabIndex - not rendered on anchor element
• ImageUrl - not supported (guidance: wrap Image in anchor instead)

Added Usage Examples

Web Forms to Blazor migration examples with styling demonstrations:

<!-- Web Forms -->
<asp:HyperLink NavigateUrl="/products" Text="View" ForeColor="#0066cc" runat="server" />

<!-- Blazor equivalent -->
<HyperLink NavigationUrl="/products" Text="View" ForeColor="#0066cc" />

All features verified against actual component implementation (HyperLink.razor, HyperLink.razor.cs, BaseStyledComponent).

Optimized GitHub Actions Workflows

• Build and Test workflow: Added paths-ignore filters to skip documentation-only changes
• Integration Tests workflow: Added paths-ignore filters to skip documentation-only changes
• Filters exclude: docs/**, **/*.md, mkdocs.yml

Documentation-only PRs now only trigger the docs workflow, while code changes continue to trigger all workflows as before. Manual workflow_dispatch triggers remain functional.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Hyperlink needs more documentation</issue_title>
<issue_description>Needs some blazor implementation details added</issue_description>

Comments on the Issue (you are @copilot in this section)

@csharpfritz Yes... the documents in the docs folder need to be updated to include information about what is supported by the current component and what needs to be done.

Jeff

On Fri, Jul 15, 2022 at 11:51 AM Hisham Bin Ateya @.***>
wrote:

He means Hyperlink component

—
Reply to this email directly, view it on GitHub
#225 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATF4NZ443S5VKS4WWPEXTVUGCJVANCNFSM4QNCPLGA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

• Fixes Hyperlink needs more documentation #225

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[csharpfritz]

@copilot Let's also update the GitHub actions for building, testing and deploying to only build and test when there are changes to the .NET code. Changes to docs like this one shouldn't trigger rebuilds and tests of the entire repository

[Copilot]

@copilot Let's also update the GitHub actions for building, testing and deploying to only build and test when there are changes to the .NET code. Changes to docs like this one shouldn't trigger rebui...

Updated in commit 4c2b7a2. Added paths-ignore filters to both build.yml and integration-tests.yml workflows to skip builds and tests when only documentation files are changed:

Filters added:

• docs/** - Documentation files
• *.md - Markdown files
• mkdocs.yml - MkDocs config

Documentation-only PRs will now only trigger the docs workflow, while code changes will continue to run all workflows as before.