dotnet-rename-client-repository-to-service

Rename client Repository to Service and migrate files, namespaces, DI registrations, and Blazor references.

8|1|Updated Feb 5, 2018
One-click install
npx skills add https://github.com/umbrella-libraries/Umbrella --skill dotnet-rename-client-repository-to-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-rename-client-repository-to-service
Source: https://github.com/umbrella-libraries/Umbrella/tree/main/.ai-shared/skills/dotnet-rename-client-repository-to-service
Command: npx skills add https://github.com/umbrella-libraries/Umbrella --skill dotnet-rename-client-repository-to-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Renames a client Repository to Service across the codebase. This move reorganizes code and aligns naming conventions to reflect a Service-oriented data layer, preparing the project for service-based data access.

Core Features & Use Cases

  • Relocates code from Web<AppName>.Web.Client.Data\Repositories to Web<AppName>.Web.Client.Data\Services while preserving the base class and all generic type parameters.
  • Updates namespaces, DI registrations, and all Blazor component references to use the new Service-based API.
  • Preserves behavioural semantics to support a smooth migration path.

Quick Start

Execute the migration by renaming the client Repository to Service across the project and update DI registrations and component references accordingly.

Frequently Asked Questions about dotnet-rename-client-repository-to-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rename a Repository to Service in a Blazor client project?

Renaming a Repository to Service involves relocating files from the Repositories folder to Services, updating namespaces, dependency injection registrations, and Blazor component references to align with the new naming convention.

What is the best way to migrate client Repository files to Services without changing behavior?

Migrating client Repository files to Services preserves the existing GenericHttpDataService base class and all generic type parameters, ensuring behavioral semantics remain unchanged while updating namespace and dependency injection registrations.

Can I update dependency injection registrations automatically when renaming a client Repository to Service?

Renaming a client Repository to Service updates dependency injection registrations to reflect the new Service-based API, ensuring the Blazor components correctly resolve the relocated data access classes.

Do I need to update Blazor component references manually after renaming a client Repository to Service?

Renaming a client Repository to Service updates all Blazor component references to use the new Service-based API, preventing manual reference updates and supporting a smooth code migration path.

Why does renaming a Repository to Service preserve the GenericHttpDataService base class?

Preserving the GenericHttpDataService base class during the Repository to Service rename ensures that all generic type parameters and behavioral semantics remain unchanged, maintaining the existing data access functionality.

Does renaming a client Repository to Service support projects using dependency injection?

Renaming a client Repository to Service fully supports projects using dependency injection by updating the DI registrations to reflect the new Service-oriented data layer and relocated namespaces.