Skip to content

[dev-v5] feat: Implement Migration Service and Resources for Fluent UI Blazor v4 to v5#4546

Open
AClerbois wants to merge 4 commits intomicrosoft:dev-v5from
AClerbois:users/aclerbois/dev-v5/add-migration-tools-to-help-agent-to-migrate-v4-to-v5
Open

[dev-v5] feat: Implement Migration Service and Resources for Fluent UI Blazor v4 to v5#4546
AClerbois wants to merge 4 commits intomicrosoft:dev-v5from
AClerbois:users/aclerbois/dev-v5/add-migration-tools-to-help-agent-to-migrate-v4-to-v5

Conversation

@AClerbois
Copy link
Collaborator

Pull Request

📖 Description

  • Added MigrationService to handle migration documentation and component migration guides.
  • Introduced MigrationResources to provide general migration overview and component-specific migration details.
  • Updated MigrationPrompts to utilize MigrationService for generating migration guidance.
  • Created MigrationTools for AI agents to access migration information programmatically.
  • Added unit tests for MigrationService, MigrationResources, and MigrationTools to ensure functionality and correctness.
  • Enhanced migration documentation with detailed guidance for components and general migration steps.

✅ Checklist

General

  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

  • I have added new tools
  • I have added Unit Tests for my new tools
  • I have modified an existing component
  • I have validated the Unit Tests for an existing component

…v4 to v5

- Added MigrationService to handle migration documentation and component migration guides.
- Introduced MigrationResources to provide general migration overview and component-specific migration details.
- Updated MigrationPrompts to utilize MigrationService for generating migration guidance.
- Created MigrationTools for AI agents to access migration information programmatically.
- Added unit tests for MigrationService, MigrationResources, and MigrationTools to ensure functionality and correctness.
- Enhanced migration documentation with detailed guidance for components and general migration steps.
@AClerbois AClerbois requested a review from vnbaaij as a code owner February 19, 2026 12:03
Copilot AI review requested due to automatic review settings February 19, 2026 12:03
@AClerbois AClerbois requested a review from dvoituron as a code owner February 19, 2026 12:03
@AClerbois AClerbois added this to the v5.0-RC2 milestone Feb 19, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a dedicated migration documentation surface to the MCP server so AI agents can retrieve a v4→v5 overview plus per-component migration guides via tools/resources/prompts.

Changes:

  • Introduces MigrationService to load migration markdown content from embedded resources and expose overview + component guides.
  • Adds MCP MigrationTools and MigrationResources for programmatic access to migration guidance.
  • Updates MigrationPrompts to generate v4→v5 guidance using MigrationService, and adds unit tests covering the new behavior.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
tests/Tools/McpServer.Tests/Tools/MigrationToolsTests.cs Adds test coverage for the new migration MCP tools output and error cases.
tests/Tools/McpServer.Tests/Services/MigrationServiceTests.cs Adds unit tests for migration doc loading, lookup behavior, and name extraction.
tests/Tools/McpServer.Tests/Resources/MigrationResourcesTests.cs Adds tests for migration MCP resources (overview, list, component lookup).
tests/Tools/McpServer.Tests/Prompts/MigrationPromptsTests.cs Updates prompt tests to use MigrationService and validates new prompt sections/behavior.
src/Tools/McpServer/Tools/MigrationTools.cs New MCP tool surface for migration overview, listing, and component guide retrieval.
src/Tools/McpServer/Services/MigrationService.cs New service that discovers/parses embedded migration markdown and exposes query APIs.
src/Tools/McpServer/Resources/MigrationResources.cs New MCP resources providing migration overview, component list, and component guide content.
src/Tools/McpServer/Prompts/MigrationPrompts.cs Switches prompts from DocumentationService to MigrationService and enriches output.
src/Tools/McpServer/Extensions/ServiceCollectionExtensions.cs Registers MigrationService in DI for prompts/tools/resources.

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

@AClerbois AClerbois changed the title feat: Implement Migration Service and Resources for Fluent UI Blazor v4 to v5 [dev-v5] feat: Implement Migration Service and Resources for Fluent UI Blazor v4 to v5 Feb 19, 2026
@AClerbois
Copy link
Collaborator Author

Both review comments have been addressed:

  1. Resource filteringLoadMigrationDocumentation() now filters on .Migration. (the folder segment) instead of just "Migration", so only files from the GetStarted/Migration/ folder are captured. This prevents MigrationVersion5.md (and any other non-component migration pages from other folders) from polluting the component migration list.

  2. Nullable parameterGetComponentMigration(string componentName) is now GetComponentMigration(string? componentName) to properly reflect the null-safe API contract in the nullable-enabled project.

All 457 tests pass after these changes.

Copy link
Collaborator Author

@AClerbois AClerbois left a comment

Choose a reason for hiding this comment

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

Both review comments have been addressed and fixes committed. All 457 tests pass.

AClerbois and others added 3 commits February 19, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants