FuSa SW Tool - Jherrod Thomas

API¶

1) Copy Clean Architecture API (starting point)¶

• Copy the Clean Arch solution into the new repo/solution.
• Rename solution + projects to your standard naming (keep it consistent with FuSa.Sw.*).

2) Namespace standardisation¶

Set root namespace everywhere to:

• Namespace: FuSa.Sw

Do this in:

• Project properties (Root Namespace / Assembly Name)
• Any *.csproj that has <RootNamespace> / <AssemblyName>
• Global usings (if you use them)
• All folders/classes where old namespaces exist (bulk replace)

3) Database naming¶

• Database name: FuSa.Sw

Update:

• appsettings.json / appsettings.Production.json connection strings

• EF Core migrations:

  • delete old migrations and create fresh for FuSa.Sw

4) Remove unnecessary code/modules¶

You specifically want to remove:

• Appointment module and all related modules

Typical cleanup areas (do in all layers):

• Domain

  • Entities, Enums, ValueObjects, Events related to appointments

• Application

  • Commands/Queries/Handlers/Validators/DTOs
  • Interfaces like IAppointmentRepository, etc.

• Infrastructure

  • Repositories, EF configs, DbSets, mapping configs
  • Any background jobs or services tied to appointments

• API

  • Controllers/endpoints
  • Authorization policies/roles only used by appointments
  • Swagger grouping / routes

Also remove:

• Unused services, unused DI registrations
• Any seed data related to removed modules

Front End¶

1) Use client’s design¶

• Treat client UI as the “source of truth”.
• Only copy in the minimum functional pieces needed from your existing FE.

2) Copy only necessary code¶

Typical “safe” items to reuse:

• Auth token handling / API base client wiring
• Shared components (toasts, loader, modal wrapper)
• Route guards
• Reusable table/grid helpers (if design allows)

Avoid copying:

• Old screens and module-specific components (especially anything appointment related)
• Extra helpers not used by the new UI

3) Use FuSa.Sw.nswag

• Copy FuSa.Sw.nswag into the FE.

• Ensure it points to:

  • correct Swagger URL (local/dev/prod)
  • correct output path (your FE’s API client folder)
  • correct namespace/module name for generated TS client (or C# client, whichever you generate)

After generation:

• Replace old API client usage with the newly generated one
• Verify compile + API calls