Executive summary
bravodev-hub/appointme falls short of our standard for a template or a sample, in part because eight passwords or keys sit in the current code. It scores 55 out of 100 and is rated Adequate, and 37 of its 46 critical findings are security problems.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 12 points. Adding tests for the code no test reaches comes next, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 60.
Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight passwords or keys in the code and three in the code's history are open to anyone who can read the repository, and seven secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The four loops of files that import each other need breaking.
The product code is 20,147 lines, about €44,000 to rebuild.
If Production Readiness rose from 41 to 52, the lowest score rated Strong, the score would rise from 55 to about 60.
New since the last survey: 8 findings
- Cyclomatic Complexity · event-calendar-views.EventCalendarViews (cyclomatic 49) src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx
- Cognitive Complexity · event-calendar-views.EventCalendarViews (cognitive 44) src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx
- God Classes · FunctionTooLong: event-calendar-views.EventCalendarViews src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx
- Dependency Vulnerabilities · REDACTED
- IaC & Container Security · REDACTED
- Code Duplication · Duplicated block (16 lines × 2 locations) src/AppointMe.Frontend/src/app/customers/columns.tsx
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 18, cognitive 13) REDACTED
- Dependency Hygiene · Unused dependency 'tailwindcss-animate'
Fixed since the last survey: 24 findings
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 10.0.10
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Xml 10.0.10
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 9.0.18 src/AppointMe.Api/AppointMe.Api.csproj
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 10.0.11 src/AppointMe.Aspire/AppointMe.Aspire.csproj
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: MessagePack 2.5.302 src/AppointMe.Aspire/AppointMe.Aspire.csproj
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] src/AppointMe.Frontend/package.json
- IaC & Container Security · High IaC: REDACTED REDACTED
- Code Duplication · Duplicated block (16 lines × 2 locations) src/AppointMe.Frontend/src/app/customers/columns.tsx
- Code Duplication · Duplicated block (6 lines × 2 locations) src/AppointMe.Frontend/src/components/format/input-formatters.ts
- Code Duplication · Duplicated block (5 lines × 10 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 12) REDACTED
- Dependency Hygiene · Unused dependency '@tanstack/pacer'
- Rich vs anemic model · Anemic entity: User src/Identity/AppointMe.Identity/Users/User.cs
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €14,000 to €73,000, for 241 to 764 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 20,147 lines of product code |
| Comment lines | The estimate prices 20,010 lines. Comment lines count towards the size of 20,147 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 AppointMe.Shared.Authorization.Roles | 2 AppointMe.Shared.Companies | 3 AppointMe.Shared.Domain | 4 AppointMe.Shared.Domain.Common | 5 AppointMe.Shared.Endpoints | 6 AppointMe.Shared.Pagination | 7 AppointMe.Shared.Users | 8 src.AppointMe_Frontend.src.api.client_schemas | 9 AppointMe.Booking.Attendees | 10 AppointMe.Booking.BookingCompanies | 11 AppointMe.Booking.ServiceProviders | 12 AppointMe.Crm.Database | 13 AppointMe.Shared.Authentication | 14 AppointMe.Shared.Authorization.Permissions.DefaultGrants | 15 AppointMe.Identity.Contracts.Identity | 16 AppointMe.Shared.Authorization.Permissions | 17 AppointMe.Booking.Appointments | 18 AppointMe.Crm.Customers | 19 AppointMe.Identity.Users | 20 AppointMe.Organizations.Employees | 21 AppointMe.Organizations.Invitations | 22 AppointMe.Organizations.Settings.Permissions | 23 AppointMe.Shared.Authorization.Principals | 24 AppointMe.Booking.Appointments.Database | 25 AppointMe.Booking.Dashboard.GetDashboardStats | 26 AppointMe.Booking.Database | 27 AppointMe.Crm.Customers.Database | 28 AppointMe.Organizations.Database | 29 AppointMe.Booking.Appointments.RescheduleAppointment | 30 AppointMe.Booking.Appointments.ScheduleAppointment | 31 AppointMe.Booking.Appointments.SeedDemoAppointments | 32 AppointMe.Booking.Attendees.ReconcileAttendees | 33 AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies | 34 AppointMe.Organizations.Companies | 35 AppointMe.Organizations.Employees.GetTeam | 36 AppointMe.Organizations.Infrastructure | 37 AppointMe.Organizations.Invitations.InviteEmployee | 38 AppointMe.Organizations.Settings.Permissions.ResetPermissions | 39 AppointMe.Organizations.Settings.Permissions.UpdatePermissions | 40 AppointMe.Organizations.Companies.Onboarding |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 AppointMe.Shared.Authorization.Roles | ||||||||||||||||||||||||||||||||||||||||
| 2 AppointMe.Shared.Companies | ||||||||||||||||||||||||||||||||||||||||
| 3 AppointMe.Shared.Domain | ||||||||||||||||||||||||||||||||||||||||
| 4 AppointMe.Shared.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 5 AppointMe.Shared.Endpoints | ||||||||||||||||||||||||||||||||||||||||
| 6 AppointMe.Shared.Pagination | ||||||||||||||||||||||||||||||||||||||||
| 7 AppointMe.Shared.Users | ||||||||||||||||||||||||||||||||||||||||
| 8 src.AppointMe_Frontend.src.api.client_schemas | ||||||||||||||||||||||||||||||||||||||||
| 9 AppointMe.Booking.Attendees | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 10 AppointMe.Booking.BookingCompanies | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 AppointMe.Booking.ServiceProviders | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 AppointMe.Crm.Database | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 AppointMe.Shared.Authentication | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 AppointMe.Shared.Authorization.Permissions.DefaultGrants | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 AppointMe.Identity.Contracts.Identity | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 AppointMe.Shared.Authorization.Permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 AppointMe.Booking.Appointments | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 18 AppointMe.Crm.Customers | 1 | 1 | 5 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 19 AppointMe.Identity.Users | 1 | 2 | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 20 AppointMe.Organizations.Employees | 2 | 2 | 1 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 21 AppointMe.Organizations.Invitations | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 22 AppointMe.Organizations.Settings.Permissions | 4 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 23 AppointMe.Shared.Authorization.Principals | 4 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 24 AppointMe.Booking.Appointments.Database | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 25 AppointMe.Booking.Dashboard.GetDashboardStats | 1 | 4 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 AppointMe.Booking.Database | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 AppointMe.Crm.Customers.Database | 1 | 1 | 2 | 8 | ||||||||||||||||||||||||||||||||||||
| 28 AppointMe.Organizations.Database | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 AppointMe.Booking.Appointments.RescheduleAppointment | 1 | 2 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 30 AppointMe.Booking.Appointments.ScheduleAppointment | 3 | 4 | 1 | 2 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 31 AppointMe.Booking.Appointments.SeedDemoAppointments | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 AppointMe.Booking.Attendees.ReconcileAttendees | 1 | 6 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 33 AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 34 AppointMe.Organizations.Companies | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 35 AppointMe.Organizations.Employees.GetTeam | 1 | 1 | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 AppointMe.Organizations.Infrastructure | 1 | 1 | 2 | 2 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||
| 37 AppointMe.Organizations.Invitations.InviteEmployee | 4 | 3 | 2 | 1 | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 AppointMe.Organizations.Settings.Permissions.ResetPermissions | 1 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 AppointMe.Organizations.Settings.Permissions.UpdatePermissions | 1 | 1 | 1 | 2 | 1 | 3 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 40 AppointMe.Organizations.Companies.Onboarding | 4 | 1 | 2 | 1 | 3 | 1 | 4 |
9→2 AppointMe.Booking.Attendees uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Attendees uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Attendees.Attendee→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Attendees uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Attendees, while a change to AppointMe.Booking.Attendees can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Attendees uses a module listed above it, which is the healthy direction.
9→3 AppointMe.Booking.Attendees uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Attendees uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Booking.Attendees.Attendee→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Booking.Attendees uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Booking.Attendees, while a change to AppointMe.Booking.Attendees can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Booking.Attendees uses a module listed above it, which is the healthy direction.
9→4 AppointMe.Booking.Attendees uses AppointMe.Shared.Domain.Common✕
- Connections
- 3 pairs of types, where a type in AppointMe.Booking.Attendees uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Attendees.Attendee→AppointMe.Shared.Domain.Common.DateOfBirthAppointMe.Booking.Attendees.Attendee→AppointMe.Shared.Domain.Common.EmailAppointMe.Booking.Attendees.Attendee→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Booking.Attendees uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Attendees, while a change to AppointMe.Booking.Attendees can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Attendees uses a module listed above it, which is the healthy direction.
10→2 AppointMe.Booking.BookingCompanies uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.BookingCompanies uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.BookingCompanies.BookingCompany→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.BookingCompanies uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.BookingCompanies, while a change to AppointMe.Booking.BookingCompanies can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.BookingCompanies uses a module listed above it, which is the healthy direction.
11→2 AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.ServiceProviders uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.ServiceProviders.ServiceProvider→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.ServiceProviders, while a change to AppointMe.Booking.ServiceProviders can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.ServiceProviders uses a module listed above it, which is the healthy direction.
11→3 AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.ServiceProviders uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Booking.ServiceProviders.ServiceProvider→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Booking.ServiceProviders, while a change to AppointMe.Booking.ServiceProviders can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Booking.ServiceProviders uses a module listed above it, which is the healthy direction.
11→4 AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Domain.Common✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.ServiceProviders uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.ServiceProviders.ServiceProvider→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Booking.ServiceProviders uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.ServiceProviders, while a change to AppointMe.Booking.ServiceProviders can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.ServiceProviders uses a module listed above it, which is the healthy direction.
12→2 AppointMe.Crm.Database uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Database uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Crm.Database.CrmDbContext→AppointMe.Shared.Companies.ICurrentCompany
- Direction
- AppointMe.Crm.Database uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Crm.Database, while a change to AppointMe.Crm.Database can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Crm.Database uses a module listed above it, which is the healthy direction.
12→18 AppointMe.Crm.Database uses AppointMe.Crm.Customers part of a loop✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Database uses a type in AppointMe.Crm.Customers.
- The types involved
AppointMe.Crm.Database.CrmDbContext→AppointMe.Crm.Customers.Customer
- Direction
- AppointMe.Crm.Database uses AppointMe.Crm.Customers, so a change to AppointMe.Crm.Customers can break AppointMe.Crm.Database, while a change to AppointMe.Crm.Database can't break AppointMe.Crm.Customers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 AppointMe.Shared.Authentication uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Shared.Authentication uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Shared.Authentication.UserIdentity→AppointMe.Shared.Domain.Common.EmailAppointMe.Shared.Authentication.UserIdentity→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Shared.Authentication uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Shared.Authentication, while a change to AppointMe.Shared.Authentication can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Shared.Authentication uses a module listed above it, which is the healthy direction.
13→7 AppointMe.Shared.Authentication uses AppointMe.Shared.Users✕
- Connections
- 3 pairs of types, where a type in AppointMe.Shared.Authentication uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Shared.Authentication.→AppointMe.Shared.Users.UserIdAppointMe.Shared.Authentication.IdentityExtensions→AppointMe.Shared.Users.UserIdAppointMe.Shared.Authentication.UserIdentity→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Shared.Authentication uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Shared.Authentication, while a change to AppointMe.Shared.Authentication can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Shared.Authentication uses a module listed above it, which is the healthy direction.
14→1 AppointMe.Shared.Authorization.Permissions.DefaultGrants uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Shared.Authorization.Permissions.DefaultGrants.RolePermissionGrant→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Shared.Authorization.Permissions.DefaultGrants uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Shared.Authorization.Permissions.DefaultGrants, while a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Permissions.DefaultGrants uses a module listed above it, which is the healthy direction.
14→16 AppointMe.Shared.Authorization.Permissions.DefaultGrants uses AppointMe.Shared.Authorization.Permissions part of a loop✕
- Connections
- 1 pair of types, where a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Shared.Authorization.Permissions.DefaultGrants.RolePermissionGrant→AppointMe.Shared.Authorization.Permissions.Permission
- Direction
- AppointMe.Shared.Authorization.Permissions.DefaultGrants uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Shared.Authorization.Permissions.DefaultGrants, while a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→4 AppointMe.Identity.Contracts.Identity uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Identity.Contracts.Identity uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Identity.Contracts.Identity.AuthenticatedUser→AppointMe.Shared.Domain.Common.EmailAppointMe.Identity.Contracts.Identity.AuthenticatedUser→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Identity.Contracts.Identity uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Identity.Contracts.Identity, while a change to AppointMe.Identity.Contracts.Identity can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Identity.Contracts.Identity uses a module listed above it, which is the healthy direction.
15→13 AppointMe.Identity.Contracts.Identity uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Identity.Contracts.Identity uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Identity.Contracts.Identity.IUserIdentityRegistry→AppointMe.Shared.Authentication.UserIdentity
- Direction
- AppointMe.Identity.Contracts.Identity uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Identity.Contracts.Identity, while a change to AppointMe.Identity.Contracts.Identity can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Identity.Contracts.Identity uses a module listed above it, which is the healthy direction.
16→1 AppointMe.Shared.Authorization.Permissions uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Shared.Authorization.Permissions uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Shared.Authorization.Permissions.PermissionRegistry→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Shared.Authorization.Permissions uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Shared.Authorization.Permissions, while a change to AppointMe.Shared.Authorization.Permissions can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Permissions uses a module listed above it, which is the healthy direction.
16→14 AppointMe.Shared.Authorization.Permissions uses AppointMe.Shared.Authorization.Permissions.DefaultGrants✕
- Connections
- 1 pair of types, where a type in AppointMe.Shared.Authorization.Permissions uses a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- The types involved
AppointMe.Shared.Authorization.Permissions.PermissionRegistry→AppointMe.Shared.Authorization.Permissions.DefaultGrants.IDefaultGrantPolicy
- Direction
- AppointMe.Shared.Authorization.Permissions uses AppointMe.Shared.Authorization.Permissions.DefaultGrants, so a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can break AppointMe.Shared.Authorization.Permissions, while a change to AppointMe.Shared.Authorization.Permissions can't break AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Permissions uses a module listed above it, which is the healthy direction.
17→2 AppointMe.Booking.Appointments uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Appointments.Appointment→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
17→3 AppointMe.Booking.Appointments uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Booking.Appointments.Appointment→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
17→4 AppointMe.Booking.Appointments uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Appointments.Appointment→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Appointments.Appointment→AppointMe.Shared.Domain.Common.LongString
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
17→9 AppointMe.Booking.Appointments uses AppointMe.Booking.Attendees✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Booking.Attendees.
- The types involved
AppointMe.Booking.Appointments.Appointment→AppointMe.Booking.Attendees.AttendeeId
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Booking.Attendees, so a change to AppointMe.Booking.Attendees can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Booking.Attendees.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
17→11 AppointMe.Booking.Appointments uses AppointMe.Booking.ServiceProviders✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Appointments.Appointment→AppointMe.Booking.ServiceProviders.ServiceProviderId
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
17→16 AppointMe.Booking.Appointments uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Booking.Appointments.AppointmentPermissions→AppointMe.Shared.Authorization.Permissions.Permission
- Direction
- AppointMe.Booking.Appointments uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Booking.Appointments, while a change to AppointMe.Booking.Appointments can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Booking.Appointments uses a module listed above it, which is the healthy direction.
18→2 AppointMe.Crm.Customers uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Crm.Customers.Customer→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Crm.Customers uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
18→3 AppointMe.Crm.Customers uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Crm.Customers.Customer→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Crm.Customers uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
18→4 AppointMe.Crm.Customers uses AppointMe.Shared.Domain.Common✕
- Connections
- 5 pairs of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Crm.Customers.Customer→AppointMe.Shared.Domain.Common.DateOfBirthAppointMe.Crm.Customers.Customer→AppointMe.Shared.Domain.Common.EmailAppointMe.Crm.Customers.Customer→AppointMe.Shared.Domain.Common.GenderAppointMe.Crm.Customers.Customer→AppointMe.Shared.Domain.Common.PersonNameAppointMe.Crm.Customers.CustomerDto→AppointMe.Shared.Domain.Common.Gender
- Direction
- AppointMe.Crm.Customers uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
18→6 AppointMe.Crm.Customers uses AppointMe.Shared.Pagination✕
- Connections
- 2 pairs of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Shared.Pagination.
- The types involved
AppointMe.Crm.Customers.CustomerRehydrationSource→AppointMe.Shared.Pagination.PagedResultAppointMe.Crm.Customers.CustomerRehydrationSource→AppointMe.Shared.Pagination.PaginationFilter
- Direction
- AppointMe.Crm.Customers uses AppointMe.Shared.Pagination, so a change to AppointMe.Shared.Pagination can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Shared.Pagination.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
18→12 AppointMe.Crm.Customers uses AppointMe.Crm.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Crm.Database.
- The types involved
AppointMe.Crm.Customers.CustomerRehydrationSource→AppointMe.Crm.Database.CrmDbContext
- Direction
- AppointMe.Crm.Customers uses AppointMe.Crm.Database, so a change to AppointMe.Crm.Database can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Crm.Database.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
18→16 AppointMe.Crm.Customers uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Crm.Customers.CustomerPermissions→AppointMe.Shared.Authorization.Permissions.Permission
- Direction
- AppointMe.Crm.Customers uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Crm.Customers, while a change to AppointMe.Crm.Customers can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Crm.Customers uses a module listed above it, which is the healthy direction.
19→3 AppointMe.Identity.Users uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Identity.Users uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Identity.Users.User→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Identity.Users uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Identity.Users, while a change to AppointMe.Identity.Users can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Identity.Users uses a module listed above it, which is the healthy direction.
19→4 AppointMe.Identity.Users uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Identity.Users uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Identity.Users.User→AppointMe.Shared.Domain.Common.EmailAppointMe.Identity.Users.User→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Identity.Users uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Identity.Users, while a change to AppointMe.Identity.Users can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Identity.Users uses a module listed above it, which is the healthy direction.
19→7 AppointMe.Identity.Users uses AppointMe.Shared.Users✕
- Connections
- 1 pair of types, where a type in AppointMe.Identity.Users uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Identity.Users.User→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Identity.Users uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Identity.Users, while a change to AppointMe.Identity.Users can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Identity.Users uses a module listed above it, which is the healthy direction.
19→13 AppointMe.Identity.Users uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Identity.Users uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Identity.Users.UserIdentityRegistry→AppointMe.Shared.Authentication.UserIdentity
- Direction
- AppointMe.Identity.Users uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Identity.Users, while a change to AppointMe.Identity.Users can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Identity.Users uses a module listed above it, which is the healthy direction.
19→15 AppointMe.Identity.Users uses AppointMe.Identity.Contracts.Identity✕
- Connections
- 5 pairs of types, where a type in AppointMe.Identity.Users uses a type in AppointMe.Identity.Contracts.Identity.
- The types involved
AppointMe.Identity.Users.→AppointMe.Identity.Contracts.Identity.AuthenticatedUserAppointMe.Identity.Users.ClaimsPrincipalExtensions→AppointMe.Identity.Contracts.Identity.AuthenticatedUserAppointMe.Identity.Users.User→AppointMe.Identity.Contracts.Identity.IdentityProviderUserIdAppointMe.Identity.Users.UserIdentityRegistry→AppointMe.Identity.Contracts.Identity.AuthenticatedUserAppointMe.Identity.Users.UserIdentityRegistry→AppointMe.Identity.Contracts.Identity.IUserIdentityRegistry
- Direction
- AppointMe.Identity.Users uses AppointMe.Identity.Contracts.Identity, so a change to AppointMe.Identity.Contracts.Identity can break AppointMe.Identity.Users, while a change to AppointMe.Identity.Users can't break AppointMe.Identity.Contracts.Identity.
- Position
- Below the diagonal: AppointMe.Identity.Users uses a module listed above it, which is the healthy direction.
20→1 AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Employees.Employee→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Employees.TeamMemberDto→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→2 AppointMe.Organizations.Employees uses AppointMe.Shared.Companies✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Employees.Employee→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Employees.EmployeeRehydrationSource→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→3 AppointMe.Organizations.Employees uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Organizations.Employees.Employee→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→4 AppointMe.Organizations.Employees uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Organizations.Employees.Employee→AppointMe.Shared.Domain.Common.EmailAppointMe.Organizations.Employees.Employee→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→7 AppointMe.Organizations.Employees uses AppointMe.Shared.Users✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Employees.Employee→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→14 AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Permissions.DefaultGrants✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- The types involved
AppointMe.Organizations.Employees.EmployeeRolesGrants→AppointMe.Shared.Authorization.Permissions.DefaultGrants.RolePermissionGrant
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Permissions.DefaultGrants, so a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→16 AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Organizations.Employees.EmployeePermissions→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Organizations.Employees.EmployeePermissions→AppointMe.Shared.Authorization.Permissions.SystemPermission
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Employees uses a module listed above it, which is the healthy direction.
20→28 AppointMe.Organizations.Employees uses AppointMe.Organizations.Database part of a loop✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Employees.EmployeeRehydrationSource→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Employees uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Employees, while a change to AppointMe.Organizations.Employees can't break AppointMe.Organizations.Database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Invitations.EmployeeInvitation→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→2 AppointMe.Organizations.Invitations uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Invitations.EmployeeInvitation→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→3 AppointMe.Organizations.Invitations uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Organizations.Invitations.EmployeeInvitation→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→4 AppointMe.Organizations.Invitations uses AppointMe.Shared.Domain.Common✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Organizations.Invitations.EmployeeInvitation→AppointMe.Shared.Domain.Common.Email
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→7 AppointMe.Organizations.Invitations uses AppointMe.Shared.Users✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Invitations.EmployeeInvitation→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→14 AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Permissions.DefaultGrants✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- The types involved
AppointMe.Organizations.Invitations.InvitationRolesGrants→AppointMe.Shared.Authorization.Permissions.DefaultGrants.RolePermissionGrant
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Permissions.DefaultGrants, so a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
21→16 AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Organizations.Invitations.InvitationPermissions→AppointMe.Shared.Authorization.Permissions.Permission
- Direction
- AppointMe.Organizations.Invitations uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Organizations.Invitations, while a change to AppointMe.Organizations.Invitations can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations uses a module listed above it, which is the healthy direction.
22→1 AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Settings.Permissions.→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicy→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicyFactory→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Settings.Permissions.RolePermissionOverride→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Settings.Permissions, while a change to AppointMe.Organizations.Settings.Permissions can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions uses a module listed above it, which is the healthy direction.
22→2 AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Companies✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Settings.Permissions.→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicy→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicyFactory→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Settings.Permissions.RolePermissionOverride→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Settings.Permissions, while a change to AppointMe.Organizations.Settings.Permissions can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions uses a module listed above it, which is the healthy direction.
22→14 AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Permissions.DefaultGrants✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions uses a type in AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- The types involved
AppointMe.Organizations.Settings.Permissions.PermissionRolesGrants→AppointMe.Shared.Authorization.Permissions.DefaultGrants.RolePermissionGrant
- Direction
- AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Permissions.DefaultGrants, so a change to AppointMe.Shared.Authorization.Permissions.DefaultGrants can break AppointMe.Organizations.Settings.Permissions, while a change to AppointMe.Organizations.Settings.Permissions can't break AppointMe.Shared.Authorization.Permissions.DefaultGrants.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions uses a module listed above it, which is the healthy direction.
22→16 AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Organizations.Settings.Permissions.PermissionPermissions→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Organizations.Settings.Permissions.PermissionPermissions→AppointMe.Shared.Authorization.Permissions.SystemPermission
- Direction
- AppointMe.Organizations.Settings.Permissions uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Organizations.Settings.Permissions, while a change to AppointMe.Organizations.Settings.Permissions can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions uses a module listed above it, which is the healthy direction.
23→1 AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 4 pairs of types, where a type in AppointMe.Shared.Authorization.Principals uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Shared.Authorization.Principals.AnonymousPrincipal→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Shared.Authorization.Principals.IPrincipal→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Shared.Authorization.Principals.SystemPrincipal→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Shared.Authorization.Principals.UserPrincipal→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Shared.Authorization.Principals, while a change to AppointMe.Shared.Authorization.Principals can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Principals uses a module listed above it, which is the healthy direction.
23→2 AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Shared.Authorization.Principals uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Shared.Authorization.Principals.UserPrincipal→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Shared.Authorization.Principals, while a change to AppointMe.Shared.Authorization.Principals can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Principals uses a module listed above it, which is the healthy direction.
23→16 AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 5 pairs of types, where a type in AppointMe.Shared.Authorization.Principals uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Shared.Authorization.Principals.AnonymousPrincipal→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Shared.Authorization.Principals.IPrincipal→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Shared.Authorization.Principals.PrincipalAuthorizationExtensions→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Shared.Authorization.Principals.SystemPrincipal→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Shared.Authorization.Principals.UserPrincipal→AppointMe.Shared.Authorization.Permissions.Permission
- Direction
- AppointMe.Shared.Authorization.Principals uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Shared.Authorization.Principals, while a change to AppointMe.Shared.Authorization.Principals can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Shared.Authorization.Principals uses a module listed above it, which is the healthy direction.
24→2 AppointMe.Booking.Appointments.Database uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.Database uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Appointments.Database.AppointmentsRepository→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Appointments.Database uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Appointments.Database, while a change to AppointMe.Booking.Appointments.Database can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.Database uses a module listed above it, which is the healthy direction.
24→4 AppointMe.Booking.Appointments.Database uses AppointMe.Shared.Domain.Common✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.Database uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Appointments.Database.AppointmentsRepository→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriod
- Direction
- AppointMe.Booking.Appointments.Database uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Appointments.Database, while a change to AppointMe.Booking.Appointments.Database can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.Database uses a module listed above it, which is the healthy direction.
24→17 AppointMe.Booking.Appointments.Database uses AppointMe.Booking.Appointments✕
- Connections
- 7 pairs of types, where a type in AppointMe.Booking.Appointments.Database uses a type in AppointMe.Booking.Appointments.
- The types involved
AppointMe.Booking.Appointments.Database.→AppointMe.Booking.Appointments.AppointmentAppointMe.Booking.Appointments.Database.→AppointMe.Booking.Appointments.AppointmentIdAppointMe.Booking.Appointments.Database.AppointmentQueries→AppointMe.Booking.Appointments.AppointmentAppointMe.Booking.Appointments.Database.AppointmentQueries→AppointMe.Booking.Appointments.AppointmentIdAppointMe.Booking.Appointments.Database.AppointmentTypeConfiguration→AppointMe.Booking.Appointments.AppointmentAppointMe.Booking.Appointments.Database.AppointmentsRepository→AppointMe.Booking.Appointments.AppointmentDtoAppointMe.Booking.Appointments.Database.AppointmentsRepository→AppointMe.Booking.Appointments.AppointmentId
- Direction
- AppointMe.Booking.Appointments.Database uses AppointMe.Booking.Appointments, so a change to AppointMe.Booking.Appointments can break AppointMe.Booking.Appointments.Database, while a change to AppointMe.Booking.Appointments.Database can't break AppointMe.Booking.Appointments.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.Database uses a module listed above it, which is the healthy direction.
25→2 AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Dashboard.GetDashboardStats uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Dashboard.GetDashboardStats.GetDashboardStatsQueryHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Dashboard.GetDashboardStats, while a change to AppointMe.Booking.Dashboard.GetDashboardStats can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Dashboard.GetDashboardStats uses a module listed above it, which is the healthy direction.
25→4 AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Domain.Common✕
- Connections
- 4 pairs of types, where a type in AppointMe.Booking.Dashboard.GetDashboardStats uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Dashboard.GetDashboardStats.DashboardStatsCalculator→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Dashboard.GetDashboardStats.DashboardStatsCalculator→AppointMe.Shared.Domain.Common.StatsBucketAppointMe.Booking.Dashboard.GetDashboardStats.GetDashboardStatsQuery→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Dashboard.GetDashboardStats.GetDashboardStatsQuery→AppointMe.Shared.Domain.Common.StatsBucket
- Direction
- AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Dashboard.GetDashboardStats, while a change to AppointMe.Booking.Dashboard.GetDashboardStats can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Dashboard.GetDashboardStats uses a module listed above it, which is the healthy direction.
25→5 AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Dashboard.GetDashboardStats uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Booking.Dashboard.GetDashboardStats.GetDashboardStatsEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Booking.Dashboard.GetDashboardStats, while a change to AppointMe.Booking.Dashboard.GetDashboardStats can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Booking.Dashboard.GetDashboardStats uses a module listed above it, which is the healthy direction.
25→11 AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Booking.ServiceProviders✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Dashboard.GetDashboardStats uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Dashboard.GetDashboardStats.DashboardStatsCalculator→AppointMe.Booking.ServiceProviders.ServiceProviderDto
- Direction
- AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Dashboard.GetDashboardStats, while a change to AppointMe.Booking.Dashboard.GetDashboardStats can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Dashboard.GetDashboardStats uses a module listed above it, which is the healthy direction.
25→23 AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Dashboard.GetDashboardStats uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Booking.Dashboard.GetDashboardStats.GetDashboardStatsQueryHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Booking.Dashboard.GetDashboardStats uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Booking.Dashboard.GetDashboardStats, while a change to AppointMe.Booking.Dashboard.GetDashboardStats can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Booking.Dashboard.GetDashboardStats uses a module listed above it, which is the healthy direction.
26→2 AppointMe.Booking.Database uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Database uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Database.BookingDbContext→AppointMe.Shared.Companies.ICurrentCompany
- Direction
- AppointMe.Booking.Database uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Database, while a change to AppointMe.Booking.Database can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Database uses a module listed above it, which is the healthy direction.
26→9 AppointMe.Booking.Database uses AppointMe.Booking.Attendees✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Database uses a type in AppointMe.Booking.Attendees.
- The types involved
AppointMe.Booking.Database.BookingDbContext→AppointMe.Booking.Attendees.Attendee
- Direction
- AppointMe.Booking.Database uses AppointMe.Booking.Attendees, so a change to AppointMe.Booking.Attendees can break AppointMe.Booking.Database, while a change to AppointMe.Booking.Database can't break AppointMe.Booking.Attendees.
- Position
- Below the diagonal: AppointMe.Booking.Database uses a module listed above it, which is the healthy direction.
26→10 AppointMe.Booking.Database uses AppointMe.Booking.BookingCompanies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Database uses a type in AppointMe.Booking.BookingCompanies.
- The types involved
AppointMe.Booking.Database.BookingDbContext→AppointMe.Booking.BookingCompanies.BookingCompany
- Direction
- AppointMe.Booking.Database uses AppointMe.Booking.BookingCompanies, so a change to AppointMe.Booking.BookingCompanies can break AppointMe.Booking.Database, while a change to AppointMe.Booking.Database can't break AppointMe.Booking.BookingCompanies.
- Position
- Below the diagonal: AppointMe.Booking.Database uses a module listed above it, which is the healthy direction.
26→11 AppointMe.Booking.Database uses AppointMe.Booking.ServiceProviders✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Database uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Database.BookingDbContext→AppointMe.Booking.ServiceProviders.ServiceProvider
- Direction
- AppointMe.Booking.Database uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Database, while a change to AppointMe.Booking.Database can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Database uses a module listed above it, which is the healthy direction.
26→17 AppointMe.Booking.Database uses AppointMe.Booking.Appointments✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Database uses a type in AppointMe.Booking.Appointments.
- The types involved
AppointMe.Booking.Database.BookingDbContext→AppointMe.Booking.Appointments.Appointment
- Direction
- AppointMe.Booking.Database uses AppointMe.Booking.Appointments, so a change to AppointMe.Booking.Appointments can break AppointMe.Booking.Database, while a change to AppointMe.Booking.Database can't break AppointMe.Booking.Appointments.
- Position
- Below the diagonal: AppointMe.Booking.Database uses a module listed above it, which is the healthy direction.
27→2 AppointMe.Crm.Customers.Database uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers.Database uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Crm.Customers.Database uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Crm.Customers.Database, while a change to AppointMe.Crm.Customers.Database can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Crm.Customers.Database uses a module listed above it, which is the healthy direction.
27→4 AppointMe.Crm.Customers.Database uses AppointMe.Shared.Domain.Common✕
- Connections
- 1 pair of types, where a type in AppointMe.Crm.Customers.Database uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriod
- Direction
- AppointMe.Crm.Customers.Database uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Crm.Customers.Database, while a change to AppointMe.Crm.Customers.Database can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Crm.Customers.Database uses a module listed above it, which is the healthy direction.
27→6 AppointMe.Crm.Customers.Database uses AppointMe.Shared.Pagination✕
- Connections
- 2 pairs of types, where a type in AppointMe.Crm.Customers.Database uses a type in AppointMe.Shared.Pagination.
- The types involved
AppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Shared.Pagination.PagedResultAppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Shared.Pagination.PaginationFilter
- Direction
- AppointMe.Crm.Customers.Database uses AppointMe.Shared.Pagination, so a change to AppointMe.Shared.Pagination can break AppointMe.Crm.Customers.Database, while a change to AppointMe.Crm.Customers.Database can't break AppointMe.Shared.Pagination.
- Position
- Below the diagonal: AppointMe.Crm.Customers.Database uses a module listed above it, which is the healthy direction.
27→18 AppointMe.Crm.Customers.Database uses AppointMe.Crm.Customers✕
- Connections
- 8 pairs of types, where a type in AppointMe.Crm.Customers.Database uses a type in AppointMe.Crm.Customers.
- The types involved
AppointMe.Crm.Customers.Database.→AppointMe.Crm.Customers.CustomerAppointMe.Crm.Customers.Database.→AppointMe.Crm.Customers.CustomerIdAppointMe.Crm.Customers.Database.CustomerQueries→AppointMe.Crm.Customers.CustomerAppointMe.Crm.Customers.Database.CustomerQueries→AppointMe.Crm.Customers.CustomerIdAppointMe.Crm.Customers.Database.CustomerRecordExtensions→AppointMe.Crm.Customers.CustomerDtoAppointMe.Crm.Customers.Database.CustomerTypeConfiguration→AppointMe.Crm.Customers.CustomerAppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Crm.Customers.CustomerDtoAppointMe.Crm.Customers.Database.CustomersRepository→AppointMe.Crm.Customers.CustomerId
- Direction
- AppointMe.Crm.Customers.Database uses AppointMe.Crm.Customers, so a change to AppointMe.Crm.Customers can break AppointMe.Crm.Customers.Database, while a change to AppointMe.Crm.Customers.Database can't break AppointMe.Crm.Customers.
- Position
- Below the diagonal: AppointMe.Crm.Customers.Database uses a module listed above it, which is the healthy direction.
28→2 AppointMe.Organizations.Database uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Database uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Database.OrganizationsDbContext→AppointMe.Shared.Companies.ICurrentCompany
- Direction
- AppointMe.Organizations.Database uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Database, while a change to AppointMe.Organizations.Database can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Database uses a module listed above it, which is the healthy direction.
28→20 AppointMe.Organizations.Database uses AppointMe.Organizations.Employees✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Database uses a type in AppointMe.Organizations.Employees.
- The types involved
AppointMe.Organizations.Database.OrganizationsDbContext→AppointMe.Organizations.Employees.Employee
- Direction
- AppointMe.Organizations.Database uses AppointMe.Organizations.Employees, so a change to AppointMe.Organizations.Employees can break AppointMe.Organizations.Database, while a change to AppointMe.Organizations.Database can't break AppointMe.Organizations.Employees.
- Position
- Below the diagonal: AppointMe.Organizations.Database uses a module listed above it, which is the healthy direction.
28→21 AppointMe.Organizations.Database uses AppointMe.Organizations.Invitations✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Database uses a type in AppointMe.Organizations.Invitations.
- The types involved
AppointMe.Organizations.Database.OrganizationsDbContext→AppointMe.Organizations.Invitations.EmployeeInvitation
- Direction
- AppointMe.Organizations.Database uses AppointMe.Organizations.Invitations, so a change to AppointMe.Organizations.Invitations can break AppointMe.Organizations.Database, while a change to AppointMe.Organizations.Database can't break AppointMe.Organizations.Invitations.
- Position
- Below the diagonal: AppointMe.Organizations.Database uses a module listed above it, which is the healthy direction.
28→22 AppointMe.Organizations.Database uses AppointMe.Organizations.Settings.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Database uses a type in AppointMe.Organizations.Settings.Permissions.
- The types involved
AppointMe.Organizations.Database.OrganizationsDbContext→AppointMe.Organizations.Settings.Permissions.RolePermissionOverride
- Direction
- AppointMe.Organizations.Database uses AppointMe.Organizations.Settings.Permissions, so a change to AppointMe.Organizations.Settings.Permissions can break AppointMe.Organizations.Database, while a change to AppointMe.Organizations.Database can't break AppointMe.Organizations.Settings.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Database uses a module listed above it, which is the healthy direction.
28→34 AppointMe.Organizations.Database uses AppointMe.Organizations.Companies part of a loop✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Database uses a type in AppointMe.Organizations.Companies.
- The types involved
AppointMe.Organizations.Database.OrganizationsDbContext→AppointMe.Organizations.Companies.Company
- Direction
- AppointMe.Organizations.Database uses AppointMe.Organizations.Companies, so a change to AppointMe.Organizations.Companies can break AppointMe.Organizations.Database, while a change to AppointMe.Organizations.Database can't break AppointMe.Organizations.Companies.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→2 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointmentCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→4 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointment→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriod
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→5 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointmentEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→11 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.ServiceProviders✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.→AppointMe.Booking.ServiceProviders.ServiceProviderIdAppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointment→AppointMe.Booking.ServiceProviders.ServiceProviderId
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→17 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.Appointments✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Booking.Appointments.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointment→AppointMe.Booking.Appointments.Appointment
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.Appointments, so a change to AppointMe.Booking.Appointments can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Booking.Appointments.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→23 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointmentCommandHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
29→26 AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.RescheduleAppointment uses a type in AppointMe.Booking.Database.
- The types involved
AppointMe.Booking.Appointments.RescheduleAppointment.RescheduleAppointmentCommandHandler→AppointMe.Booking.Database.BookingDbContext
- Direction
- AppointMe.Booking.Appointments.RescheduleAppointment uses AppointMe.Booking.Database, so a change to AppointMe.Booking.Database can break AppointMe.Booking.Appointments.RescheduleAppointment, while a change to AppointMe.Booking.Appointments.RescheduleAppointment can't break AppointMe.Booking.Database.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.RescheduleAppointment uses a module listed above it, which is the healthy direction.
30→2 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Companies✕
- Connections
- 3 pairs of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Shared.Companies.CompanyIdAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Shared.Companies.CompanyIdAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointmentCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→4 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Domain.Common✕
- Connections
- 4 pairs of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Shared.Domain.Common.LongStringAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Shared.Domain.Common.DateTimeOffsetPeriodAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Shared.Domain.Common.LongString
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→5 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointmentEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→9 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Attendees✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Booking.Attendees.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Booking.Attendees.AttendeeIdAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Booking.Attendees.AttendeeId
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Attendees, so a change to AppointMe.Booking.Attendees can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Booking.Attendees.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→11 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.ServiceProviders✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Booking.ServiceProviders.ServiceProviderIdAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Booking.ServiceProviders.ServiceProviderId
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→17 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Appointments✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Booking.Appointments.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.→AppointMe.Booking.Appointments.AppointmentAppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointment→AppointMe.Booking.Appointments.Appointment
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Appointments, so a change to AppointMe.Booking.Appointments can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Booking.Appointments.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→23 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointmentCommandHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
30→26 AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.ScheduleAppointment uses a type in AppointMe.Booking.Database.
- The types involved
AppointMe.Booking.Appointments.ScheduleAppointment.ScheduleAppointmentCommandHandler→AppointMe.Booking.Database.BookingDbContext
- Direction
- AppointMe.Booking.Appointments.ScheduleAppointment uses AppointMe.Booking.Database, so a change to AppointMe.Booking.Database can break AppointMe.Booking.Appointments.ScheduleAppointment, while a change to AppointMe.Booking.Appointments.ScheduleAppointment can't break AppointMe.Booking.Database.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.ScheduleAppointment uses a module listed above it, which is the healthy direction.
31→2 AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Shared.Companies✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.Appointments.SeedDemoAppointments uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointments→AppointMe.Shared.Companies.CompanyIdAppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointmentsCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Appointments.SeedDemoAppointments, while a change to AppointMe.Booking.Appointments.SeedDemoAppointments can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.SeedDemoAppointments uses a module listed above it, which is the healthy direction.
31→9 AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Attendees✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.SeedDemoAppointments uses a type in AppointMe.Booking.Attendees.
- The types involved
AppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointments→AppointMe.Booking.Attendees.AttendeeId
- Direction
- AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Attendees, so a change to AppointMe.Booking.Attendees can break AppointMe.Booking.Appointments.SeedDemoAppointments, while a change to AppointMe.Booking.Appointments.SeedDemoAppointments can't break AppointMe.Booking.Attendees.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.SeedDemoAppointments uses a module listed above it, which is the healthy direction.
31→11 AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.ServiceProviders✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.SeedDemoAppointments uses a type in AppointMe.Booking.ServiceProviders.
- The types involved
AppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointments→AppointMe.Booking.ServiceProviders.ServiceProviderId
- Direction
- AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.ServiceProviders, so a change to AppointMe.Booking.ServiceProviders can break AppointMe.Booking.Appointments.SeedDemoAppointments, while a change to AppointMe.Booking.Appointments.SeedDemoAppointments can't break AppointMe.Booking.ServiceProviders.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.SeedDemoAppointments uses a module listed above it, which is the healthy direction.
31→17 AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Appointments✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.SeedDemoAppointments uses a type in AppointMe.Booking.Appointments.
- The types involved
AppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointments→AppointMe.Booking.Appointments.Appointment
- Direction
- AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Appointments, so a change to AppointMe.Booking.Appointments can break AppointMe.Booking.Appointments.SeedDemoAppointments, while a change to AppointMe.Booking.Appointments.SeedDemoAppointments can't break AppointMe.Booking.Appointments.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.SeedDemoAppointments uses a module listed above it, which is the healthy direction.
31→26 AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Appointments.SeedDemoAppointments uses a type in AppointMe.Booking.Database.
- The types involved
AppointMe.Booking.Appointments.SeedDemoAppointments.SeedDemoAppointmentsCommandHandler→AppointMe.Booking.Database.BookingDbContext
- Direction
- AppointMe.Booking.Appointments.SeedDemoAppointments uses AppointMe.Booking.Database, so a change to AppointMe.Booking.Database can break AppointMe.Booking.Appointments.SeedDemoAppointments, while a change to AppointMe.Booking.Appointments.SeedDemoAppointments can't break AppointMe.Booking.Database.
- Position
- Below the diagonal: AppointMe.Booking.Appointments.SeedDemoAppointments uses a module listed above it, which is the healthy direction.
32→2 AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Attendees.ReconcileAttendees uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.Attendees.ReconcileAttendees.ReconcileAttendeesCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.Attendees.ReconcileAttendees, while a change to AppointMe.Booking.Attendees.ReconcileAttendees can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.Attendees.ReconcileAttendees uses a module listed above it, which is the healthy direction.
32→4 AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Shared.Domain.Common✕
- Connections
- 6 pairs of types, where a type in AppointMe.Booking.Attendees.ReconcileAttendees uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Booking.Attendees.ReconcileAttendees.→AppointMe.Shared.Domain.Common.DateOfBirthAppointMe.Booking.Attendees.ReconcileAttendees.→AppointMe.Shared.Domain.Common.EmailAppointMe.Booking.Attendees.ReconcileAttendees.→AppointMe.Shared.Domain.Common.PersonNameAppointMe.Booking.Attendees.ReconcileAttendees.UpsertAttendee→AppointMe.Shared.Domain.Common.DateOfBirthAppointMe.Booking.Attendees.ReconcileAttendees.UpsertAttendee→AppointMe.Shared.Domain.Common.EmailAppointMe.Booking.Attendees.ReconcileAttendees.UpsertAttendee→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Booking.Attendees.ReconcileAttendees, while a change to AppointMe.Booking.Attendees.ReconcileAttendees can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Booking.Attendees.ReconcileAttendees uses a module listed above it, which is the healthy direction.
32→9 AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Booking.Attendees✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.Attendees.ReconcileAttendees uses a type in AppointMe.Booking.Attendees.
- The types involved
AppointMe.Booking.Attendees.ReconcileAttendees.UpsertAttendee→AppointMe.Booking.Attendees.Attendee
- Direction
- AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Booking.Attendees, so a change to AppointMe.Booking.Attendees can break AppointMe.Booking.Attendees.ReconcileAttendees, while a change to AppointMe.Booking.Attendees.ReconcileAttendees can't break AppointMe.Booking.Attendees.
- Position
- Below the diagonal: AppointMe.Booking.Attendees.ReconcileAttendees uses a module listed above it, which is the healthy direction.
32→26 AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Booking.Database✕
- Connections
- 6 pairs of types, where a type in AppointMe.Booking.Attendees.ReconcileAttendees uses a type in AppointMe.Booking.Database.
- The types involved
AppointMe.Booking.Attendees.ReconcileAttendees.AttendeeReconciliationJob→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.Attendees.ReconcileAttendees.AttendeeSynchronizer→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.Attendees.ReconcileAttendees.CustomerDeletedEventHandler→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.Attendees.ReconcileAttendees.CustomerRegisteredEventHandler→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.Attendees.ReconcileAttendees.CustomerUpdatedEventHandler→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.Attendees.ReconcileAttendees.ReconcileAttendeesCommandHandler→AppointMe.Booking.Database.BookingDbContext
- Direction
- AppointMe.Booking.Attendees.ReconcileAttendees uses AppointMe.Booking.Database, so a change to AppointMe.Booking.Database can break AppointMe.Booking.Attendees.ReconcileAttendees, while a change to AppointMe.Booking.Attendees.ReconcileAttendees can't break AppointMe.Booking.Database.
- Position
- Below the diagonal: AppointMe.Booking.Attendees.ReconcileAttendees uses a module listed above it, which is the healthy direction.
33→2 AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Shared.Companies✕
- Connections
- 2 pairs of types, where a type in AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.→AppointMe.Shared.Companies.CompanyIdAppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.UpsertBookingCompany→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies, while a change to AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a module listed above it, which is the healthy direction.
33→10 AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Booking.BookingCompanies✕
- Connections
- 1 pair of types, where a type in AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a type in AppointMe.Booking.BookingCompanies.
- The types involved
AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.UpsertBookingCompany→AppointMe.Booking.BookingCompanies.BookingCompany
- Direction
- AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Booking.BookingCompanies, so a change to AppointMe.Booking.BookingCompanies can break AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies, while a change to AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies can't break AppointMe.Booking.BookingCompanies.
- Position
- Below the diagonal: AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a module listed above it, which is the healthy direction.
33→26 AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Booking.Database✕
- Connections
- 3 pairs of types, where a type in AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a type in AppointMe.Booking.Database.
- The types involved
AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.BookingCompanySynchronizer→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.CompanyRegisteredEventHandler→AppointMe.Booking.Database.BookingDbContextAppointMe.Booking.BookingCompanies.ReconcileBookingCompanies.ReconcileBookingCompaniesCommandHandler→AppointMe.Booking.Database.BookingDbContext
- Direction
- AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses AppointMe.Booking.Database, so a change to AppointMe.Booking.Database can break AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies, while a change to AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies can't break AppointMe.Booking.Database.
- Position
- Below the diagonal: AppointMe.Booking.BookingCompanies.ReconcileBookingCompanies uses a module listed above it, which is the healthy direction.
34→1 AppointMe.Organizations.Companies uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Companies.CompanyOwnership→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
34→2 AppointMe.Organizations.Companies uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Companies.Company→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
34→3 AppointMe.Organizations.Companies uses AppointMe.Shared.Domain✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Shared.Domain.
- The types involved
AppointMe.Organizations.Companies.Company→AppointMe.Shared.Domain.AggregateRoot
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Shared.Domain, so a change to AppointMe.Shared.Domain can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Shared.Domain.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
34→7 AppointMe.Organizations.Companies uses AppointMe.Shared.Users✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Companies.Company→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
34→20 AppointMe.Organizations.Companies uses AppointMe.Organizations.Employees✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Organizations.Employees.
- The types involved
AppointMe.Organizations.Companies.Company→AppointMe.Organizations.Employees.EmployeeIdAppointMe.Organizations.Companies.CompanyOwnership→AppointMe.Organizations.Employees.EmployeeId
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Organizations.Employees, so a change to AppointMe.Organizations.Employees can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Organizations.Employees.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
34→28 AppointMe.Organizations.Companies uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Companies.CompanyRehydrationSource→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Companies uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Companies, while a change to AppointMe.Organizations.Companies can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Companies uses a module listed above it, which is the healthy direction.
35→2 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamQueryHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→5 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→6 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Pagination✕
- Connections
- 3 pairs of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Shared.Pagination.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamQuery→AppointMe.Shared.Pagination.PaginationFilterAppointMe.Organizations.Employees.GetTeam.GetTeamRequest→AppointMe.Shared.Pagination.PaginationRequestAppointMe.Organizations.Employees.GetTeam.GetTeamResponse→AppointMe.Shared.Pagination.PagedResult
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Pagination, so a change to AppointMe.Shared.Pagination can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Shared.Pagination.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→13 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamQueryHandler→AppointMe.Shared.Authentication.IIdentity
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→20 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Organizations.Employees✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Organizations.Employees.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamResponse→AppointMe.Organizations.Employees.TeamMemberDto
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Organizations.Employees, so a change to AppointMe.Organizations.Employees can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Organizations.Employees.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→23 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamQueryHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
35→28 AppointMe.Organizations.Employees.GetTeam uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Employees.GetTeam uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Employees.GetTeam.GetTeamQueryHandler→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Employees.GetTeam uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Employees.GetTeam, while a change to AppointMe.Organizations.Employees.GetTeam can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Employees.GetTeam uses a module listed above it, which is the healthy direction.
36→1 AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Infrastructure.PermissionResolver→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→2 AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Infrastructure.UserPrincipalFactory→AppointMe.Shared.Companies.ICurrentCompany
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→13 AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authentication✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Infrastructure.CurrentPrincipalResolver→AppointMe.Shared.Authentication.IIdentityResolverAppointMe.Organizations.Infrastructure.UserPrincipalFactory→AppointMe.Shared.Authentication.UserIdentity
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→16 AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Organizations.Infrastructure.PermissionResolver→AppointMe.Shared.Authorization.Permissions.PermissionAppointMe.Organizations.Infrastructure.PermissionResolver→AppointMe.Shared.Authorization.Permissions.PermissionRegistry
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→22 AppointMe.Organizations.Infrastructure uses AppointMe.Organizations.Settings.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Organizations.Settings.Permissions.
- The types involved
AppointMe.Organizations.Infrastructure.PermissionResolver→AppointMe.Organizations.Settings.Permissions.RolePermissionOverride
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Organizations.Settings.Permissions, so a change to AppointMe.Organizations.Settings.Permissions can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Organizations.Settings.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→23 AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Organizations.Infrastructure.CurrentPrincipalResolver→AppointMe.Shared.Authorization.Principals.ICurrentPrincipalAppointMe.Organizations.Infrastructure.CurrentPrincipalResolver→AppointMe.Shared.Authorization.Principals.ICurrentPrincipalResolverAppointMe.Organizations.Infrastructure.CurrentPrincipalResolver→AppointMe.Shared.Authorization.Principals.IPrincipalAppointMe.Organizations.Infrastructure.UserPrincipalFactory→AppointMe.Shared.Authorization.Principals.UserPrincipal
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
36→28 AppointMe.Organizations.Infrastructure uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Infrastructure uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Infrastructure.UserPrincipalFactory→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Infrastructure uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Infrastructure, while a change to AppointMe.Organizations.Infrastructure can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Infrastructure uses a module listed above it, which is the healthy direction.
37→1 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployee→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeCommand→AppointMe.Shared.Authorization.Roles.RoleAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeRequest→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→2 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Companies✕
- Connections
- 3 pairs of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployee→AppointMe.Shared.Companies.CompanyIdAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→4 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Domain.Common✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.→AppointMe.Shared.Domain.Common.EmailAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployee→AppointMe.Shared.Domain.Common.Email
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→5 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→7 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Users✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.→AppointMe.Shared.Users.UserIdAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployee→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→13 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeCommandHandler→AppointMe.Shared.Authentication.IIdentity
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→21 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Organizations.Invitations✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Organizations.Invitations.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.→AppointMe.Organizations.Invitations.EmployeeInvitationAppointMe.Organizations.Invitations.InviteEmployee.InviteEmployee→AppointMe.Organizations.Invitations.EmployeeInvitation
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Organizations.Invitations, so a change to AppointMe.Organizations.Invitations can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Organizations.Invitations.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→23 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeCommandHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
37→28 AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Invitations.InviteEmployee uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Invitations.InviteEmployee.InviteEmployeeCommandHandler→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Invitations.InviteEmployee uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Invitations.InviteEmployee, while a change to AppointMe.Organizations.Invitations.InviteEmployee can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Invitations.InviteEmployee uses a module listed above it, which is the healthy direction.
38→2 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissionsCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→5 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissionsEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→7 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Users✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.→AppointMe.Shared.Users.UserIdAppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissions→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→13 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissionsCommandHandler→AppointMe.Shared.Authentication.IIdentity
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→22 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Organizations.Settings.Permissions✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Organizations.Settings.Permissions.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissions→AppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicy
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Organizations.Settings.Permissions, so a change to AppointMe.Organizations.Settings.Permissions can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Organizations.Settings.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→23 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissionsCommandHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
38→28 AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Settings.Permissions.ResetPermissions.ResetPermissionsCommandHandler→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Settings.Permissions.ResetPermissions uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Settings.Permissions.ResetPermissions, while a change to AppointMe.Organizations.Settings.Permissions.ResetPermissions can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.ResetPermissions uses a module listed above it, which is the healthy direction.
39→1 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Authorization.Roles.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.RolePermissionGrantDto→AppointMe.Shared.Authorization.Roles.Role
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Roles, so a change to AppointMe.Shared.Authorization.Roles can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Authorization.Roles.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→2 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Companies✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Companies.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsCommandHandler→AppointMe.Shared.Companies.CompanyId
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Companies, so a change to AppointMe.Shared.Companies can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→5 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→7 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Users✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.→AppointMe.Shared.Users.UserIdAppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissions→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→13 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsCommandHandler→AppointMe.Shared.Authentication.IIdentity
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→16 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Permissions✕
- Connections
- 3 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Authorization.Permissions.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.→AppointMe.Shared.Authorization.Permissions.PermissionRegistryAppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissions→AppointMe.Shared.Authorization.Permissions.PermissionRegistryAppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsCommandHandler→AppointMe.Shared.Authorization.Permissions.PermissionRegistry
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Permissions, so a change to AppointMe.Shared.Authorization.Permissions can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Authorization.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→22 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Organizations.Settings.Permissions✕
- Connections
- 3 pairs of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Organizations.Settings.Permissions.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.→AppointMe.Organizations.Settings.Permissions.RolePermissionOverrideAppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissions→AppointMe.Organizations.Settings.Permissions.CompanyPermissionPolicyAppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissions→AppointMe.Organizations.Settings.Permissions.RolePermissionOverride
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Organizations.Settings.Permissions, so a change to AppointMe.Organizations.Settings.Permissions can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Organizations.Settings.Permissions.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→23 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Principals✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Shared.Authorization.Principals.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsCommandHandler→AppointMe.Shared.Authorization.Principals.IPrincipal
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Shared.Authorization.Principals, so a change to AppointMe.Shared.Authorization.Principals can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Shared.Authorization.Principals.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
39→28 AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Settings.Permissions.UpdatePermissions.UpdatePermissionsCommandHandler→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Settings.Permissions.UpdatePermissions, while a change to AppointMe.Organizations.Settings.Permissions.UpdatePermissions can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Settings.Permissions.UpdatePermissions uses a module listed above it, which is the healthy direction.
40→4 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Domain.Common✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Shared.Domain.Common.
- The types involved
AppointMe.Organizations.Companies.Onboarding.→AppointMe.Shared.Domain.Common.EmailAppointMe.Organizations.Companies.Onboarding.→AppointMe.Shared.Domain.Common.PersonNameAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Shared.Domain.Common.EmailAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Shared.Domain.Common.PersonName
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Domain.Common, so a change to AppointMe.Shared.Domain.Common can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Shared.Domain.Common.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→5 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Endpoints✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Shared.Endpoints.
- The types involved
AppointMe.Organizations.Companies.Onboarding.OnboardingEndpoint→AppointMe.Shared.Endpoints.IEndpoint
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Endpoints, so a change to AppointMe.Shared.Endpoints can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Shared.Endpoints.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→7 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Users✕
- Connections
- 2 pairs of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Shared.Users.
- The types involved
AppointMe.Organizations.Companies.Onboarding.→AppointMe.Shared.Users.UserIdAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Shared.Users.UserId
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Users, so a change to AppointMe.Shared.Users can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Shared.Users.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→13 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Authentication✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Shared.Authentication.
- The types involved
AppointMe.Organizations.Companies.Onboarding.OnboardingCommandHandler→AppointMe.Shared.Authentication.IIdentity
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Shared.Authentication, so a change to AppointMe.Shared.Authentication can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Shared.Authentication.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→20 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Employees✕
- Connections
- 3 pairs of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Organizations.Employees.
- The types involved
AppointMe.Organizations.Companies.Onboarding.→AppointMe.Organizations.Employees.EmployeeAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Organizations.Employees.EmployeeAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Organizations.Employees.EmployeeId
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Employees, so a change to AppointMe.Organizations.Employees can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Organizations.Employees.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→28 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Database✕
- Connections
- 1 pair of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Organizations.Database.
- The types involved
AppointMe.Organizations.Companies.Onboarding.OnboardingCommandHandler→AppointMe.Organizations.Database.OrganizationsDbContext
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Database, so a change to AppointMe.Organizations.Database can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Organizations.Database.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
40→34 AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Companies✕
- Connections
- 4 pairs of types, where a type in AppointMe.Organizations.Companies.Onboarding uses a type in AppointMe.Organizations.Companies.
- The types involved
AppointMe.Organizations.Companies.Onboarding.→AppointMe.Organizations.Companies.CompanyAppointMe.Organizations.Companies.Onboarding.→AppointMe.Organizations.Companies.CompanyNameAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Organizations.Companies.CompanyAppointMe.Organizations.Companies.Onboarding.Onboarding→AppointMe.Organizations.Companies.CompanyName
- Direction
- AppointMe.Organizations.Companies.Onboarding uses AppointMe.Organizations.Companies, so a change to AppointMe.Organizations.Companies can break AppointMe.Organizations.Companies.Onboarding, while a change to AppointMe.Organizations.Companies.Onboarding can't break AppointMe.Organizations.Companies.
- Position
- Below the diagonal: AppointMe.Organizations.Companies.Onboarding uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 56 | Medium |
| A05:2025 — Injection | 27 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (2), REDACTED; Add tests that import the unreached modules (directly or through their public entry); Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (2), REDACTED. | +11.6 pts | Low | Secret Scanning |
| Add tests that import the unreached modules (directly or through their public entry). | +6.4 pts | Medium | Test Coverage |
| Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down. | +3.0 pts | Medium | Outbound HTTP resilience |
| Bump outdated dependencies to current versions to limit upgrade debt. | +2.0 pts | Medium | Dependency Freshness |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +1.6 pts | Medium | A11y enforcement |
| Resolve the 1 redundant comment finding(s) in Comment Value — start with sidebar.tsx. | +0.7 pts | Low | Comment Value |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.4 pts | Medium | Forms & labels |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +1.4 pts | Medium | Visual & motion safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.6 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| src/Booking/AppointMe.Booking/Attendees/ReconcileAttendees/CustomerRegisteredEventHandler.cs | 6.7 | Near-clean | Explicit Debt: Dead code: CustomerRegisteredEventHandler |
| src/Booking/AppointMe.Booking/ServiceProviders/ReconcileServiceProviders/EmployeeRegisteredEventHandler.cs | 6.7 | Near-clean | Explicit Debt: Dead code: EmployeeRegisteredEventHandler |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx | 7.4 | Near-clean | Cyclomatic Complexity: event-calendar-views.EventCalendarViews (cyclomatic 49) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 109 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 109 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 298 of 312 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 145 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 2 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1 deducted marker(s) and the 1.9/KLoC density on this row were taken over this repository's .NET projects ALONE: .tsx (10,139 lines, 50% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/AppointMe.Api/Antiforgery/AntiforgeryMiddleware.cs`, `src/AppointMe.Api/Authentication/CurrentIdentityResolver.cs`, `src/AppointMe.Api/Authentication/DemoLogin/EntraExternalIdDemoUserAuthenticator.cs`, `src/AppointMe.Api/Authentication/DemoLogin/KeycloakDemoUserAuthenticator.cs`, `src/AppointMe.Api/Authentication/HttpIdentityFactory.cs`, … (+117 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container appointme-keycloak exited (137); runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was event-calendar-views.EventCalendarViews at 49.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with event-calendar-views.EventCalendarViews (cyclomatic 49). — Refactoring it lifts Cyclomatic Complexity from 8.4 to about 9.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was event-calendar-views.EventCalendarViews at 44.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with event-calendar-views.EventCalendarViews (cognitive 44). — Refactoring it lifts Cognitive Complexity from 8.5 to about 8.9/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
11 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 10 FunctionTooLong finding(s) in God Classes — start with schedule-appointment-dialog.tsx, event-calendar-views.tsx, trend-chart.tsx. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with sidebar.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
10 duplicated block group(s) detected. Measured on part of this repository only: .tsx (50% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with EmployeeRegisteredEventHandler.cs, BookingCompanyTypeConfiguration.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (14–20 lines × 2) finding(s) in Code Duplication — start with EntraExternalIdClaimsTransformer.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18 lines × 3) finding(s) in Code Duplication — start with AttendeeTypeConfiguration.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
18 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D9 · Test Distribution
175 test methods: 175 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 175 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
6 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 48 direct `PackageReference`(s), and 202 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted debt markers + 78 dead symbols across 8987 LoC in the .NET projects (1.9/KLoC) → score 6.3. Measured on the .NET source only: .tsx (50% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 78 Dead code finding(s) in Explicit Debt — start with CrmDefaultGrantPolicy.cs, DeleteCustomerCommandHandler.cs, DeleteCustomerEndpoint.cs. — One of this dimension's main actionable groups (78 warning-level).
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 12 document(s) read across 13 unit(s).
D23 · Boundary Type-Coupling
No domain types are scored-flagged across 8 context boundaries; 2 contract project(s) carry advisory strong-ID notes. Contexts: AppointMe, AppointMe.Aspire, AppointMe.Booking, AppointMe.Crm, AppointMe.Identity, AppointMe.Organizations, AppointMe.Shared, AppointMe.Templates.
D24 · Comment Value
1 of 93 judged comments only repeat the code they sit on (1.1 %). 8 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with sidebar.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 18 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with AppointMe.Booking.csproj, AppointMe.Shared.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Split AppointMe.Shared finding(s) in Project Cohesion — start with AppointMe.Shared.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
27 finding(s): 0 critical, 25 high, 2 medium, 0 low. semgrep hit a parse error in 125 file(s) — `src/AppointMe.Api.Tests/Authorization/SuperAdminAuthorizationHandlerTests.cs` (lines 58–59, line 65), `src/AppointMe.Api/Antiforgery/AntiforgeryMiddleware.cs` (lines 7–9, line 10), `src/AppointMe.Api/Authentication/CurrentIdentityResolver.cs` (lines 3–4, lines 5–6), `src/AppointMe.Api/Authentication/DemoLogin/EntraExternalIdDemoUserAuthenticator.cs` (lines 14–15, line 16, line 17, …), `src/AppointMe.Api/Authentication/DemoLogin/KeycloakDemoUserAuthenticator.cs` (lines 9–11, lines 12–13), … (+120 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 114 of those file(s) — `src/AppointMe.Api.Tests/Authorization/SuperAdminAuthorizationHandlerTests.cs`, `src/AppointMe.Api/Antiforgery/AntiforgeryMiddleware.cs`, `src/AppointMe.Api/Authentication/CurrentIdentityResolver.cs`, `src/AppointMe.Api/Authentication/DemoLogin/EntraExternalIdDemoUserAuthenticator.cs`, `src/AppointMe.Api/Authentication/DemoLogin/KeycloakDemoUserAuthenticator.cs`, … (+109 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 5 of those file(s) — `src/AppointMe.Shared/Domain/Errors/AccessDeniedException.cs`, `src/AppointMe.Shared/Domain/Errors/ConflictException.cs`, `src/AppointMe.Shared/Domain/Errors/NotFoundException.cs`, `src/AppointMe.Shared/Domain/Errors/ValidationException.cs`, `src/AppointMe.Shared/Pagination/PagedResult.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
56 finding(s): 0 critical, 0 high, 55 medium, 1 low.
What to do
- Resolve the 55 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (25), REDACTED (10), REDACTED (4). — One of this dimension's main actionable groups (55 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 23 of the 473 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:166, src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx:21
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
AC4 · Keyboard semantics
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/AppointMe.Frontend/src/components/ui/input.tsx:6
- <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/AppointMe.Frontend/src/components/ui/textarea.tsx:6
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 129 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — src/AppointMe.Frontend/package.json:79
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces AppointMe.Shared.Authorization.Permissions ↔ AppointMe.Shared.Authorization.Permissions.DefaultGrants depend on each other. The lightest dependency in the cycle is AppointMe.Shared.Authorization.Permissions → AppointMe.Shared.Authorization.Permissions.DefaultGrants (AppointMe.Shared.Authorization.Permissions.PermissionRegistry → AppointMe.Shared.Authorization.Permissions.DefaultGrants.IDefaultGrantPolicy, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/AppointMe.Shared/Authorization/Permissions/PermissionRegistry.cs:1
- The namespaces AppointMe.Crm.Customers ↔ AppointMe.Crm.Database depend on each other. The lightest dependency in the cycle is AppointMe.Crm.Customers → AppointMe.Crm.Database (AppointMe.Crm.Customers.CustomerRehydrationSource → AppointMe.Crm.Database.CrmDbContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/CRM/AppointMe.Crm/Customers/CustomerRehydrationSource.cs:3
- The namespaces AppointMe.Identity.Database ↔ AppointMe.Identity.Users depend on each other. The lightest dependency in the cycle is AppointMe.Identity.Database → AppointMe.Identity.Users (AppointMe.Identity.Database.IdentityDbContext → AppointMe.Identity.Users.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Identity/AppointMe.Identity/Database/IdentityDbContext.cs:1
- The namespaces AppointMe.Organizations.Companies ↔ AppointMe.Organizations.Database ↔ AppointMe.Organizations.Employees depend on each other. The lightest dependency in the cycle is AppointMe.Organizations.Companies → AppointMe.Organizations.Database (AppointMe.Organizations.Companies.CompanyRehydrationSource → AppointMe.Organizations.Database.OrganizationsDbContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Organizations/AppointMe.Organizations/Companies/CompanyRehydrationSource.cs:2
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `OnboardingCommandHandler.HandleAsync` saves `Company`, `Employee` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Organizations/AppointMe.Organizations/Companies/Onboarding/OnboardingCommandHandler.cs:7
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `UserRegisteredEvent.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Identity/AppointMe.Identity/Users/RegisterUser/UserRegisteredEvent.cs:5
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
- `Customer` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/CRM/AppointMe.Crm/Customers/Customer.cs:4
- `Company` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Organizations/AppointMe.Organizations/Companies/Company.cs:7
- `Employee` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Organizations/AppointMe.Organizations/Employees/Employee.cs:6
- `EmployeeInvitation` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Organizations/AppointMe.Organizations/Invitations/EmployeeInvitation.cs:6
- `Appointment` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Booking/AppointMe.Booking/Appointments/Appointment.cs:6
- `Attendee` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Booking/AppointMe.Booking/Attendees/Attendee.cs:4
- `ServiceProvider` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Booking/AppointMe.Booking/ServiceProviders/ServiceProvider.cs:4
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Customer` exposes publicly writable state (Name, DateOfBirth, Gender, Email, IsDeleted). — src/CRM/AppointMe.Crm/Customers/Customer.cs:4
- `Company` exposes publicly writable state (PrimaryOwnerEmployeeId). — src/Organizations/AppointMe.Organizations/Companies/Company.cs:7
- `Employee` exposes publicly writable state (Roles, IsDeleted). — src/Organizations/AppointMe.Organizations/Employees/Employee.cs:6
- `EmployeeInvitation` exposes publicly writable state (Status, AcceptedAt). — src/Organizations/AppointMe.Organizations/Invitations/EmployeeInvitation.cs:6
- `Appointment` exposes publicly writable state (ProviderId, Period, Status). — src/Booking/AppointMe.Booking/Appointments/Appointment.cs:6
- `Attendee` exposes publicly writable state (Name, DateOfBirth, Email, IsDeleted). — src/Booking/AppointMe.Booking/Attendees/Attendee.cs:4
- `ServiceProvider` exposes publicly writable state (Name, IsDeleted). — src/Booking/AppointMe.Booking/ServiceProviders/ServiceProvider.cs:4
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
- AppointMe.Organizations.Invitations.EmployeeInvitation's [Email, Status] are judged in AppointMe.Organizations.Invitations.GetPendingInvitations.GetPendingInvitationsQueryHandler, AppointMe.Organizations.Me.GetCurrentUserQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
- Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
ED1 · Handler temporal coupling
ED3 · Event naming
ED4 · Outbox / dual-write
ED5 · Idempotency
- `RegisterCustomer.RegisterCustomerCommandHandler.HandleAsync` mutates persistent state (a database save) and inserts a new `Customer` with a fresh id (`NewId()` → `Guid.CreateVersion7()`) (line 24), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommandHandler.cs:10
- `AcceptInvitation.AcceptInvitationCommandHandler.HandleAsync` mutates persistent state (a database save) and inserts a new `Employee` with a fresh id (`NewId()` → `Guid.CreateVersion7()`) (line 34), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Organizations/AppointMe.Organizations/Invitations/AcceptInvitation/AcceptInvitationCommandHandler.cs:10
- `Signup.SignupCommandHandler.HandleAsync` mutates persistent state (a database save) and inserts a new `User` with a fresh id (`NewId()` → `Guid.CreateVersion7()`) (line 40), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Identity/AppointMe.Identity/Signup/SignupCommandHandler.cs:16
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `HasRole` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/AppointMe.Shared/Authorization/Principals/AnonymousPrincipal.cs:8
- `HasPermission` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/AppointMe.Shared/Authorization/Principals/AnonymousPrincipal.cs:9
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a README to the 11 of 12 project(s) that lack one — worth up to 1.8 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/CODE_REVIEW_REPORT.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CODE_REVIEW_REPORT.md:225
What to do
- Reconcile the README with reality: docs/CODE_REVIEW_REPORT.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3.
P1 · CI/CD gates
P10 · Library API & versioning
- 27/31 types (87%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability
- Only 5/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `services.AddHttpClient<IDemoUserAuthenticator, KeycloakDemoUserAuthenticator>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/AppointMe.Api/Authentication/DemoLogin/DemoModeExtensions.cs:22
- `services.AddHttpClient<IDemoUserAuthenticator, EntraExternalIdDemoUserAuthent...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/AppointMe.Api/Authentication/DemoLogin/DemoModeExtensions.cs:25
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 10 duplicated blocks under src/AppointMe.Frontend/src/app/ have copies in at least two of the sibling directories appointments, auth, customers, invitations, onboarding, team — 6 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/AppointMe.Frontend/src/app/customers/customers.tsx:95
- src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:47 · src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:75 — the two spans are one implementation copied and then locally edited — 708 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:47
- src/AppointMe.Frontend/src/components/ui/context-menu.tsx:81 · src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/context-menu.tsx:81
- src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:104 · src/AppointMe.Frontend/src/components/ui/menubar.tsx:123 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:104
- src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:35 · src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:36 — the two spans are one implementation copied and then locally edited — 317 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:35
- src/AppointMe.Frontend/src/app/customers/create-customer.tsx:85 · src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:117 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/customers/create-customer.tsx:85
- src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:42 · src/AppointMe.Frontend/src/components/ui/dialog.tsx:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:42
- src/AppointMe.Frontend/src/components/ui/context-menu.tsx:25 · src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:153 · src/AppointMe.Frontend/src/components/ui/menubar.tsx:172 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/context-menu.tsx:25
- src/AppointMe.Frontend/src/components/ui/carousel.tsx:161 · src/AppointMe.Frontend/src/components/ui/carousel.tsx:191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/AppointMe.Frontend/src/components/ui/carousel.tsx:161
- src/AppointMe.Frontend/src/app/customers/customers.tsx:95 · src/AppointMe.Frontend/src/app/team/team.tsx:122 — the two spans are one implementation copied and then locally edited — 125 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/AppointMe.Frontend/src/app/customers/customers.tsx:95
- src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:92 · src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:131 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:92
- src/AppointMe.Frontend/src/components/ui/drawer.tsx:72 · src/AppointMe.Frontend/src/components/ui/sheet.tsx:76 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/drawer.tsx:72
- src/AppointMe.Frontend/src/components/ui/alert.tsx:29 · src/AppointMe.Frontend/src/components/ui/field.tsx:110 · src/AppointMe.Frontend/src/components/ui/input-group.tsx:117 · src/AppointMe.Frontend/src/components/ui/table.tsx:47 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert.tsx:29
- src/AppointMe.Frontend/src/app/customers/columns.tsx:7 · src/AppointMe.Frontend/src/app/team/columns.tsx:6 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/customers/columns.tsx:7
- src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:157 · src/AppointMe.Frontend/src/components/signup/signup-form.tsx:129 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:157
- src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61 · src/AppointMe.Frontend/src/components/ui/avatar.tsx:5 · src/AppointMe.Frontend/src/components/ui/command.tsx:85 · src/AppointMe.Frontend/src/components/ui/context-menu.tsx:168 · +7 more site(s) not listed — the 11 copies are spread across 11 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61
- src/AppointMe.Frontend/src/components/ui/button-group.tsx:23 · src/AppointMe.Frontend/src/components/ui/field.tsx:75 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/button-group.tsx:23
- src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:24 · src/AppointMe.Frontend/src/app/team/actions-cell.tsx:84 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:24
- src/AppointMe.Frontend/src/components/format/timezone.ts:1 · src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/format/timezone.ts:1
- src/AppointMe.Frontend/src/components/ui/empty.tsx:42 · src/AppointMe.Frontend/src/components/ui/item.tsx:80 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/empty.tsx:42
- src/AppointMe.Frontend/src/components/ui/hover-card.tsx:7 · src/AppointMe.Frontend/src/components/ui/popover.tsx:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/hover-card.tsx:7
- src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:111 · src/AppointMe.Frontend/src/components/signup/signup-form.tsx:98 · src/AppointMe.Frontend/src/components/signup/signup-form.tsx:117 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:111
- src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:214 · src/AppointMe.Frontend/src/app/customers/create-customer.tsx:85 · src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:117 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:214
- src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:56 · src/AppointMe.Frontend/src/app/customers/customers.tsx:35 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:56
- src/AppointMe.Frontend/src/components/ui/field.tsx:73 · src/AppointMe.Frontend/src/components/ui/input-group.tsx:55 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/field.tsx:73
- src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:241 · src/AppointMe.Frontend/src/app/customers/create-customer.tsx:75 · src/AppointMe.Frontend/src/app/customers/create-customer.tsx:118 · src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:102 · +4 more site(s) not listed — the 8 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:241
- src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:45 · src/AppointMe.Frontend/src/components/ui/alert.tsx:23 · src/AppointMe.Frontend/src/components/ui/card.tsx:36 · src/AppointMe.Frontend/src/components/ui/dialog.tsx:67 · +4 more site(s) not listed — the 8 copies are spread across 7 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:45
- src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:150 · src/AppointMe.Frontend/src/components/ui/menubar.tsx:169 · src/AppointMe.Frontend/src/components/ui/resizable.tsx:10 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:150
- src/AppointMe.Frontend/src/components/ui/select.tsx:117 · src/AppointMe.Frontend/src/components/ui/select.tsx:129 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/select.tsx:117
- src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:76 · src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:64 · src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:89 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:76
- src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:103 · src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:106 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:103
- src/AppointMe.Frontend/src/components/ui/accordion.tsx:10 · src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:67 · src/AppointMe.Frontend/src/components/ui/avatar.tsx:5 · src/AppointMe.Frontend/src/components/ui/command.tsx:91 · +9 more site(s) not listed — the 13 copies are spread across 12 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/accordion.tsx:10
- src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:51 · src/AppointMe.Frontend/src/components/ui/command.tsx:108 · src/AppointMe.Frontend/src/components/ui/context-menu.tsx:178 · src/AppointMe.Frontend/src/components/ui/dialog.tsx:73 · +10 more site(s) not listed — the 14 copies are spread across 11 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:51
- src/AppointMe.Frontend/src/app/auth/signup/signup.tsx:10 · src/AppointMe.Frontend/src/app/invitations/invitations.tsx:59 · src/AppointMe.Frontend/src/app/onboarding/onboarding.tsx:8 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/AppointMe.Frontend/src/app/auth/signup/signup.tsx:10
- src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:63 · src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:96 · src/AppointMe.Frontend/src/components/modal-dialog/confirm-dialog.tsx:30 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:63
- src/AppointMe.Frontend/src/app/layouts/sidebar/nav-user.tsx:35 · src/AppointMe.Frontend/src/app/layouts/sidebar/nav-user.tsx:53 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/AppointMe.Frontend/src/app/layouts/sidebar/nav-user.tsx:35
- src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61 · src/AppointMe.Frontend/src/components/ui/avatar.tsx:9 · src/AppointMe.Frontend/src/components/ui/command.tsx:85 · src/AppointMe.Frontend/src/components/ui/context-menu.tsx:168 · +8 more site(s) not listed — the 12 copies are spread across 12 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61
- src/AppointMe.Frontend/src/components/ui/avatar.tsx:1 · src/AppointMe.Frontend/src/components/ui/label.tsx:3 · src/AppointMe.Frontend/src/components/ui/resizable.tsx:2 · src/AppointMe.Frontend/src/components/ui/switch.tsx:3 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/AppointMe.Frontend/src/components/ui/avatar.tsx:1
- src/AppointMe.Frontend/src/components/ui/breadcrumb.tsx:18 · src/AppointMe.Frontend/src/components/ui/card.tsx:25 · src/AppointMe.Frontend/src/components/ui/card.tsx:43 · src/AppointMe.Frontend/src/components/ui/drawer.tsx:67 · +3 more site(s) not listed — the 7 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/breadcrumb.tsx:18
- src/AppointMe.Frontend/src/components/ui/drawer.tsx:73 · src/AppointMe.Frontend/src/components/ui/radio-group.tsx:9 · src/AppointMe.Frontend/src/components/ui/sheet.tsx:77 · src/AppointMe.Frontend/src/components/ui/tabs.tsx:8 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AppointMe.Frontend/src/components/ui/drawer.tsx:73
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- TrendChart has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:72
- (anonymous) has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:168
- ActionsCell has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/AppointMe.Frontend/src/app/team/actions-cell.tsx:22
- getPayloadConfigFromPayload has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:299
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- src/AppointMe.Frontend/src/components/ui/sidebar.tsx has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/AppointMe.Frontend/src/components/ui/sidebar.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 159 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 59 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- 1 file(s) (~17 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
R8 · Dependency Hygiene
- Declared in src/AppointMe.Frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/AppointMe.Frontend/src/app/layouts/header/header.tsx → src/AppointMe.Frontend/src/app/router/index.ts → src/AppointMe.Frontend/src/app/router/router.tsx → src/AppointMe.Frontend/src/app/layouts/index.ts → src/AppointMe.Frontend/src/app/layouts/layout.tsx → src/AppointMe.Frontend/src/app/layouts/header/index.ts → src/AppointMe.Frontend/src/app/layouts/header/header.tsx (one verified cycle inside a mutually-dependent group of 9 files) — src/AppointMe.Frontend/src/app/layouts/header/header.tsx:2
- src/AppointMe.Frontend/src/components/auth/can.tsx → src/AppointMe.Frontend/src/components/auth/index.ts → src/AppointMe.Frontend/src/components/auth/can.tsx (one verified cycle inside a mutually-dependent group of 3 files) — src/AppointMe.Frontend/src/components/auth/can.tsx:2
- src/AppointMe.Frontend/src/components/theme/index.ts → src/AppointMe.Frontend/src/components/theme/mode-toggle.tsx → src/AppointMe.Frontend/src/components/theme/index.ts — src/AppointMe.Frontend/src/components/theme/index.ts:2
- src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx → src/AppointMe.Frontend/src/components/ui/index.ts → src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx (one verified cycle inside a mutually-dependent group of 3 files) — src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx:1
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- Set: Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.) — src/AppointMe.Api/SecurityHeaders/SecurityHeadersMiddleware.cs:27
What to do
- Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
- `RedirectStandardOutput` is set here, but `StandardOutput` is not being read when the code waits for the child to exit — it is never read, read only later, or read only in part. The child blocks as soon as it fills the StandardOutput pipe (~4 KB, never more than 64 KB), so it never finishes and never exits, and the read or wait above never returns: a `WaitForExit` timeout after a read does not help: the timeout bounds the WAIT, not the read that precedes it. Drain every redirected stream before blocking on the child — read one on a background thread (`BeginOutputReadLine()` with its `DataReceived` handler, or a `Task` running `ReadToEndAsync()` started before the other read and awaited after it) — or stop redirecting the stream you do not consume. — src/AppointMe.Aspire/DevCertificate.cs:22
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `_graph` (line 15) holds a `GraphServiceClient` that `EntraIdentityProvider` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `EntraIdentityProvider` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_graph` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `EntraIdentityProvider`. Implement `IDisposable` and release `_graph` there, or take the instance from the caller so its owner ends it. — src/Identity/AppointMe.Identity/Entra/EntraIdentityProvider.cs:15
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `Object.entries(THEMES).map(([theme,prefix])=>` ${prefix} [data-chart=${id}] { ${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:84
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 74% | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Adequate — gated by D13, R4, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 73% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Accessibility | 63% | Strong | Solid. |
| Performance | 77% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 32 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container appointme-keycloak exited (137); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .ts, .tsx, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 27 exposed C# types.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 122 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/AppointMe.Shared/Authorization/Permissions/PermissionRegistry.cs:1
- Namespace dependency cycle src/CRM/AppointMe.Crm/Customers/CustomerRehydrationSource.cs:3
- Namespace dependency cycle src/Identity/AppointMe.Identity/Database/IdentityDbContext.cs:1
- Namespace dependency cycle src/Organizations/AppointMe.Organizations/Companies/CompanyRehydrationSource.cs:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/AppointMe.Frontend/src/components/auth/can.tsx:2
- Import cycle (2 files) src/AppointMe.Frontend/src/components/theme/index.ts:2
- Import cycle (2 files) src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx:1
- NoWarnInCsproj Directory.Build.props:13
- REDACTED
- Import cycle (6 files) src/AppointMe.Frontend/src/app/layouts/header/header.tsx:2
Serious — 239 finding(s)
- Dead code: CrmDefaultGrantPolicy src/CRM/AppointMe.Crm/Authorization/CrmDefaultGrantPolicy.cs:7
- Dead code: DeleteCustomerCommandHandler src/CRM/AppointMe.Crm/Customers/DeleteCustomer/DeleteCustomerCommandHandler.cs:6
- Dead code: DeleteCustomerEndpoint src/CRM/AppointMe.Crm/Customers/DeleteCustomer/DeleteCustomerEndpoint.cs:4
- Dead code: GetCustomerByIdEndpoint src/CRM/AppointMe.Crm/Customers/GetCustomerById/GetCustomerByIdEndpoint.cs:4
- Dead code: GetCustomerByIdQueryHandler src/CRM/AppointMe.Crm/Customers/GetCustomerById/GetCustomerByIdQueryHandler.cs:5
- Dead code: GetCustomerQueryHandler src/CRM/AppointMe.Crm/Customers/GetCustomers/GetCustomerQueryHandler.cs:6
- Dead code: GetCustomersEndpoint src/CRM/AppointMe.Crm/Customers/GetCustomers/GetCustomersEndpoint.cs:5
- Dead code: GetNewCustomerStatsEndpoint src/CRM/AppointMe.Crm/Customers/GetNewCustomerStats/GetNewCustomerStatsEndpoint.cs:3
- Dead code: RegisterCustomerCommandHandler src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommandHandler.cs:5
- Dead code: RegisterCustomerEndpoint src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerEndpoint.cs:6
- Dead code: TopUpDemoCustomersCommandHandler src/CRM/AppointMe.Crm/Customers/TopUpDemoCustomers/TopUpDemoCustomersCommandHandler.cs:5
- Dead code: TopUpDemoCustomersJobRegistrar src/CRM/AppointMe.Crm/Customers/TopUpDemoCustomers/TopUpDemoCustomersJobRegistrar.cs:6
- Dead code: UpdateCustomerCommandHandler src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerCommandHandler.cs:6
- Dead code: UpdateCustomerEndpoint src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerEndpoint.cs:5
- Dead code: HasRole src/AppointMe.Shared/Authorization/Principals/IPrincipal.cs:8
- Dead code: OrganizationsDefaultGrantPolicy src/Organizations/AppointMe.Organizations/Authorization/OrganizationsDefaultGrantPolicy.cs:8
- Dead code: OnboardingCommandHandler src/Organizations/AppointMe.Organizations/Companies/Onboarding/OnboardingCommandHandler.cs:5
- Dead code: OnboardingEndpoint src/Organizations/AppointMe.Organizations/Companies/Onboarding/OnboardingEndpoint.cs:6
- Dead code: DeleteEmployeeCommandHandler src/Organizations/AppointMe.Organizations/Employees/DeleteEmployee/DeleteEmployeeCommandHandler.cs:6
- Dead code: DeleteEmployeeEndpoint src/Organizations/AppointMe.Organizations/Employees/DeleteEmployee/DeleteEmployeeEndpoint.cs:3
- Dead code: GetTeamEndpoint src/Organizations/AppointMe.Organizations/Employees/GetTeam/GetTeamEndpoint.cs:5
- Dead code: GetTeamQueryHandler src/Organizations/AppointMe.Organizations/Employees/GetTeam/GetTeamQueryHandler.cs:10
- Dead code: UpdateEmployeeRolesCommandHandler src/Organizations/AppointMe.Organizations/Employees/UpdateEmployeeRoles/UpdateEmployeeRolesCommandHandler.cs:8
- Dead code: UpdateEmployeeRolesEndpoint src/Organizations/AppointMe.Organizations/Employees/UpdateEmployeeRoles/UpdateEmployeeRolesEndpoint.cs:5
- Dead code: AcceptInvitationCommandHandler src/Organizations/AppointMe.Organizations/Invitations/AcceptInvitation/AcceptInvitationCommandHandler.cs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: schedule-appointment-dialog.ScheduleAppointmentDialog src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:51
- FunctionTooLong: event-calendar-views.EventCalendarViews src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx:65
- FunctionTooLong: trend-chart.TrendChart src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:72
- FunctionTooLong: edit-customer-dialog.EditCustomerDialog src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:44
- FunctionTooLong: create-customer.CreateCustomer src/AppointMe.Frontend/src/app/customers/create-customer.tsx:24
- FunctionTooLong: team.Team src/AppointMe.Frontend/src/app/team/team.tsx:26
- FunctionTooLong: reschedule-appointment-dialog.RescheduleAppointmentDialog src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:36
- FunctionTooLong: signup-form.SignupForm src/AppointMe.Frontend/src/components/signup/signup-form.tsx:22
- FunctionTooLong: appointments.Appointments src/AppointMe.Frontend/src/app/appointments/appointments.tsx:22
- FunctionTooLong: onboarding-form.OnboardingForm src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:55
- Anemic entity: Customer src/CRM/AppointMe.Crm/Customers/Customer.cs:4
- Anemic entity: Company src/Organizations/AppointMe.Organizations/Companies/Company.cs:7
- Anemic entity: Employee src/Organizations/AppointMe.Organizations/Employees/Employee.cs:6
- Anemic entity: EmployeeInvitation src/Organizations/AppointMe.Organizations/Invitations/EmployeeInvitation.cs:6
- Anemic entity: Appointment src/Booking/AppointMe.Booking/Appointments/Appointment.cs:6
- Anemic entity: Attendee src/Booking/AppointMe.Booking/Attendees/Attendee.cs:4
- Anemic entity: ServiceProvider src/Booking/AppointMe.Booking/ServiceProviders/ServiceProvider.cs:4
- Duplicated block (14 lines × 2 locations) src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:24
- Duplicated block (14 lines × 2 locations) src/AppointMe.Frontend/src/components/format/timezone.ts:1
- Duplicated block (14 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/empty.tsx:42
- Duplicated block (14 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/hover-card.tsx:7
- Non-idempotent mutation: RegisterCustomer.RegisterCustomerCommandHandler.HandleAsync src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommandHandler.cs:10
- Non-idempotent mutation: AcceptInvitation.AcceptInvitationCommandHandler.HandleAsync src/Organizations/AppointMe.Organizations/Invitations/AcceptInvitation/AcceptInvitationCommandHandler.cs:10
- Non-idempotent mutation: Signup.SignupCommandHandler.HandleAsync src/Identity/AppointMe.Identity/Signup/SignupCommandHandler.cs:16
- <Select> field component without a label src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:166
- <Select> field component without a label src/AppointMe.Frontend/src/components/ui/data-table-pagination.tsx:21
- Focus outline removed inline src/AppointMe.Frontend/src/components/ui/input.tsx:6
- Focus outline removed inline src/AppointMe.Frontend/src/components/ui/textarea.tsx:6
- Duplicated block (11 lines × 2) src/Booking/AppointMe.Booking/ServiceProviders/ReconcileServiceProviders/EmployeeRegisteredEventHandler.cs:11
- Duplicated block (11 lines × 2) src/Booking/AppointMe.Booking/BookingCompanies/Database/BookingCompanyTypeConfiguration.cs:9
- Hollow method — returns a constant without doing the work src/AppointMe.Shared/Authorization/Principals/AnonymousPrincipal.cs:8
- Hollow method — returns a constant without doing the work src/AppointMe.Shared/Authorization/Principals/AnonymousPrincipal.cs:9
- Outbound HTTP without resilience src/AppointMe.Api/Authentication/DemoLogin/DemoModeExtensions.cs:22
- Outbound HTTP without resilience src/AppointMe.Api/Authentication/DemoLogin/DemoModeExtensions.cs:25
- Duplicated block (16 lines × 2 locations) src/AppointMe.Frontend/src/app/customers/columns.tsx:7
- Duplicated block (16 lines × 2 locations) src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:157
- Duplicated block (11 lines × 8 locations) src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:241
- Duplicated block (11 lines × 8 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:45
- Accessibility enforcement below the top rung src/AppointMe.Frontend/package.json:79
- event-calendar-views.EventCalendarViews (cyclomatic 49) src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx:65
- trend-chart.TrendChart (cyclomatic 29) src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:72
- chart.ChartTooltipContent (cyclomatic 22) REDACTED:105
- actions-cell.ActionsCell (cyclomatic 18) src/AppointMe.Frontend/src/app/team/actions-cell.tsx:22
- event-calendar-views.EventCalendarViews (cognitive 44) src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx:65
- trend-chart.TrendChart (cognitive 28) src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:72
- chart.ChartTooltipContent (cognitive 22) REDACTED:105
- invite-employee-dialog.InviteEmployeeDialog (cognitive 19) src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:36
- signup-form.SignupForm (cognitive 17) src/AppointMe.Frontend/src/components/signup/signup-form.tsx:22
- REDACTED
- REDACTED
- FileTooLong: ui/sidebar.tsx src/AppointMe.Frontend/src/components/ui/sidebar.tsx
- Duplicated block (14–20 lines × 2) src/AppointMe.Api/Authentication/EntraExternalId/EntraExternalIdClaimsTransformer.cs:9
- Duplicated block (18 lines × 3) src/Booking/AppointMe.Booking/Attendees/Database/AttendeeTypeConfiguration.cs:15
- Duplicated block (14 lines × 2) src/Identity/AppointMe.Identity/Users/Database/UserTypeConfiguration.cs:31
- Duplicated block (15 lines × 5) src/Booking/AppointMe.Booking/Attendees/Database/AttendeeTypeConfiguration.cs:21
- Duplicated block (12 lines × 2) src/Organizations/AppointMe.Organizations/Employees/Database/EmployeeTypeConfiguration.cs:17
- Duplicated block (12–13 lines × 2) src/Booking/AppointMe.Booking/Attendees/ReconcileAttendees/CustomerRegisteredEventHandler.cs:10
- Duplicated block (7 lines × 2) src/Organizations/AppointMe.Organizations/Employees/Database/EmployeeTypeConfiguration.cs:43
- Duplicated block (6 lines × 2) src/Booking/AppointMe.Booking/Dashboard/GetDashboardStats/GetDashboardStatsRequest.cs:5
- Coverage not measured — test suite did not build
- One operation mutates 2 aggregates: OnboardingCommandHandler.HandleAsync src/Organizations/AppointMe.Organizations/Companies/Onboarding/OnboardingCommandHandler.cs:7
- Duplication concentrated across 6 sibling directories (10 clone groups) src/AppointMe.Frontend/src/app/customers/customers.tsx:95
- Duplicated block with local edits (106 matched lines × 2 locations) src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:47
- Duplicated block (102 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/context-menu.tsx:81
- Duplicated block (79 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:104
- Duplicated block with local edits (51 matched lines × 2 locations) src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:35
- Duplicated block (47 lines × 2 locations) src/AppointMe.Frontend/src/app/customers/create-customer.tsx:85
- Duplicated block (34 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:42
- Duplicated block (33 lines × 3 locations) src/AppointMe.Frontend/src/components/ui/context-menu.tsx:25
- Duplicated block (29 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/carousel.tsx:161
- Duplicated block with local edits (24 matched lines × 2 locations) src/AppointMe.Frontend/src/app/customers/customers.tsx:95
- Duplicated block (23 lines × 2 locations) src/AppointMe.Frontend/src/app/team/edit-employee-roles-dialog.tsx:92
- Duplicated block (21 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/drawer.tsx:72
- Duplicated block (17 lines × 4 locations) src/AppointMe.Frontend/src/components/ui/alert.tsx:29
- Duplicated block (15 lines × 11 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61
- Duplicated block (15 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/button-group.tsx:23
- Duplicated block (13 lines × 3 locations) src/AppointMe.Frontend/src/components/onboarding/onboarding-form.tsx:111
- Duplicated block (12 lines × 3 locations) src/AppointMe.Frontend/src/app/appointments/schedule-appointment/schedule-appointment-dialog.tsx:214
- Duplicated block with local edits (12 matched lines × 2 locations) src/AppointMe.Frontend/src/app/customers/actions-cell.tsx:56
- Duplicated block (12 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/field.tsx:73
- Duplicated block (11 lines × 3 locations) src/AppointMe.Frontend/src/components/ui/dropdown-menu.tsx:150
- Duplicated block (11 lines × 2 locations) src/AppointMe.Frontend/src/components/ui/select.tsx:117
- Duplicated block (10 lines × 3 locations) src/AppointMe.Frontend/src/app/customers/edit-customer-dialog.tsx:76
- Duplicated block (10 lines × 2 locations) src/AppointMe.Frontend/src/app/team/invite-employee-dialog.tsx:103
- Duplicated block (10 lines × 13 locations) src/AppointMe.Frontend/src/components/ui/accordion.tsx:10
- Duplicated block (10 lines × 14 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:51
- Duplicated block (9 lines × 3 locations) src/AppointMe.Frontend/src/app/auth/signup/signup.tsx:10
- Duplicated block (8 lines × 3 locations) src/AppointMe.Frontend/src/app/appointments/reschedule-appointment/reschedule-appointment-dialog.tsx:63
- Duplicated block (8 lines × 2 locations) src/AppointMe.Frontend/src/app/layouts/sidebar/nav-user.tsx:35
- Duplicated block (8 lines × 12 locations) src/AppointMe.Frontend/src/components/ui/alert-dialog.tsx:61
- Duplicated block (8 lines × 4 locations) src/AppointMe.Frontend/src/components/ui/avatar.tsx:1
- Duplicated block (8 lines × 7 locations) src/AppointMe.Frontend/src/components/ui/breadcrumb.tsx:18
- Duplicated block (7 lines × 4 locations) src/AppointMe.Frontend/src/components/ui/drawer.tsx:73
- Complex function TrendChart (cyclomatic 22, cognitive 20) src/AppointMe.Frontend/src/app/dashboard/trend-chart.tsx:72
- Complex function (anonymous) (cyclomatic 18, cognitive 13) REDACTED:168
- Complex function ActionsCell (cyclomatic 15, cognitive 14) src/AppointMe.Frontend/src/app/team/actions-cell.tsx:22
- Complex function getPayloadConfigFromPayload (cyclomatic 12, cognitive 11) REDACTED:299
- src/AppointMe.Frontend/src/components/ui/sidebar.tsx: 627 lines of code src/AppointMe.Frontend/src/components/ui/sidebar.tsx:1
- Test Coverage
- Dependency Freshness
- Unused dependency 'baseline-browser-mapping'
- Unused dependency 'openapi-types'
- Unused dependency 'tailwindcss-animate'
- Redirected process stream is never drained (deadlock) src/AppointMe.Aspire/DevCertificate.cs:22
- Disposable acquired into a field and never released src/Identity/AppointMe.Identity/Entra/EntraIdentityProvider.cs:15
- Untrusted text written into markup unescaped REDACTED:84
Minor — 24 finding(s)
- Mutable entity: Customer src/CRM/AppointMe.Crm/Customers/Customer.cs:4
- Mutable entity: Company src/Organizations/AppointMe.Organizations/Companies/Company.cs:7
- Mutable entity: Employee src/Organizations/AppointMe.Organizations/Employees/Employee.cs:6
- Mutable entity: EmployeeInvitation src/Organizations/AppointMe.Organizations/Invitations/EmployeeInvitation.cs:6
- Mutable entity: Appointment src/Booking/AppointMe.Booking/Appointments/Appointment.cs:6
- Mutable entity: Attendee src/Booking/AppointMe.Booking/Attendees/Attendee.cs:4
- Mutable entity: ServiceProvider src/Booking/AppointMe.Booking/ServiceProviders/ServiceProvider.cs:4
- Projects may be oversized for their cohesion src/Booking/AppointMe.Booking/AppointMe.Booking.csproj:1
- Projects may be oversized for their cohesion src/AppointMe.Shared/AppointMe.Shared.csproj:1
- Duplicated predicate src/Organizations/AppointMe.Organizations/Invitations/GetPendingInvitations/GetPendingInvitationsQueryHandler.cs:22
- Duplicated predicate src/AppointMe.Frontend/src/app/customers/columns.tsx:12
- redundant comment src/AppointMe.Frontend/src/components/ui/sidebar.tsx:73
- Split AppointMe.Shared src/AppointMe.Shared/AppointMe.Shared.csproj:1
- REDACTED
- REDACTED
- Primitive id on a domain type: UserRegisteredEvent.UserId src/Identity/AppointMe.Identity/Users/RegisterUser/UserRegisteredEvent.cs:5
- Rule about [Email, Status] decided in 2 places
- No ADRs
- README/code drift docs/CODE_REVIEW_REPORT.md:225
- Large public API surface
- Logging is not universal
- No performance benchmarks
- Security headers incomplete src/AppointMe.Api/SecurityHeaders/SecurityHeadersMiddleware.cs:27
- Silent fallback default on configuration miss src/AppointMe.Api/Authentication/DemoLogin/DemoModeExtensions.cs:18
Minor — 3 finding(s)
- AppointMe.Identity: 2 contract type(s) expose producer-owned ids/enums
- AppointMe.Organizations: 4 contract type(s) expose producer-owned ids/enums
- Off the main sequence: AppointMe.Shared src/AppointMe.Shared/AppointMe.Shared.csproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a8a9469eaa4f45b1a408bea1da46910d/history.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a8a9469eaa4f45b1a408bea1da46910d/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/AppointMe.Frontend/src/api --exclude src/Booking/AppointMe.Booking/Database/Migrations --exclude src/CRM/AppointMe.Crm/Database/Migrations --exclude src/Identity/AppointMe.Identity/Database/Migrations --exclude src/Organizations/AppointMe.Organizations/Database/Migrations . | 27 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list AppointMe.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 56 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 122 file(s) — `src/AppointMe.Api/Antiforgery/AntiforgeryMiddleware.cs`, `src/AppointMe.Api/Authentication/CurrentIdentityResolver.cs`, `src/AppointMe.Api/Authentication/DemoLogin/EntraExternalIdDemoUserAuthenticator.cs`, `src/AppointMe.Api/Authentication/DemoLogin/KeycloakDemoUserAuthenticator.cs`, `src/AppointMe.Api/Authentication/HttpIdentityFactory.cs`, … (+117 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Name — 40 field(s)
- PersonName.FirstName src/AppointMe.Shared/Domain/Common/PersonName.cs:5
- PersonName.LastName src/AppointMe.Shared/Domain/Common/PersonName.cs:5
- FullName src/AppointMe.Shared/Domain/Common/PersonName.cs:15
- AppointmentDto.ProviderFirstName src/Booking/AppointMe.Booking/Appointments/AppointmentDto.cs:10
- AppointmentDto.ProviderLastName src/Booking/AppointMe.Booking/Appointments/AppointmentDto.cs:11
- AppointmentDto.AttendeeFirstName src/Booking/AppointMe.Booking/Appointments/AppointmentDto.cs:15
- AppointmentDto.AttendeeLastName src/Booking/AppointMe.Booking/Appointments/AppointmentDto.cs:16
- ServiceProviderDto.FirstName src/Booking/AppointMe.Booking/ServiceProviders/ServiceProviderDto.cs:6
- ServiceProviderDto.LastName src/Booking/AppointMe.Booking/ServiceProviders/ServiceProviderDto.cs:7
- ServiceProviderDto.FullName src/Booking/AppointMe.Booking/ServiceProviders/ServiceProviderDto.cs:8
- CustomerSnapshot.FirstName src/CRM/AppointMe.Crm.Contracts/Customers/CustomerSnapshot.cs:6
- CustomerSnapshot.LastName src/CRM/AppointMe.Crm.Contracts/Customers/CustomerSnapshot.cs:7
- CustomerRegisteredEvent.FirstName src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerRegisteredEvent.cs:8
- CustomerRegisteredEvent.LastName src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerRegisteredEvent.cs:9
- CustomerUpdatedEvent.FirstName src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerUpdatedEvent.cs:8
- CustomerUpdatedEvent.LastName src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerUpdatedEvent.cs:9
- CustomerDto.FullName src/CRM/AppointMe.Crm/Customers/CustomerDto.cs:6
- CustomerDto.FirstName src/CRM/AppointMe.Crm/Customers/CustomerDto.cs:7
- CustomerDto.LastName src/CRM/AppointMe.Crm/Customers/CustomerDto.cs:8
- CustomerRecord.FirstName src/CRM/AppointMe.Crm/Customers/Database/CustomerRecord.cs:6
- CustomerRecord.LastName src/CRM/AppointMe.Crm/Customers/Database/CustomerRecord.cs:7
- RegisterCustomerCommand.FirstName src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommand.cs:5
- RegisterCustomerCommand.LastName src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommand.cs:6
- RegisterCustomerRequest.FirstName src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerRequest.cs:5
- RegisterCustomerRequest.LastName src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerRequest.cs:6
- UpdateCustomerCommand.FirstName src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerCommand.cs:6
- UpdateCustomerCommand.LastName src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerCommand.cs:7
- UpdateCustomerRequest.FirstName src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerRequest.cs:5
- UpdateCustomerRequest.LastName src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerRequest.cs:6
- EmployeeRegistered.FirstName src/Organizations/AppointMe.Organizations.Contracts/Employees/Events/EmployeeRegistered.cs:9
- EmployeeRegistered.LastName src/Organizations/AppointMe.Organizations.Contracts/Employees/Events/EmployeeRegistered.cs:10
- EmployeeRolesUpdated.FirstName src/Organizations/AppointMe.Organizations.Contracts/Employees/Events/EmployeeRolesUpdated.cs:9
- EmployeeRolesUpdated.LastName src/Organizations/AppointMe.Organizations.Contracts/Employees/Events/EmployeeRolesUpdated.cs:10
- EmployeeSnapshot.FirstName src/Organizations/AppointMe.Organizations.Contracts/Employees/IEmployeeRehydrationSource.cs:9
- EmployeeSnapshot.LastName src/Organizations/AppointMe.Organizations.Contracts/Employees/IEmployeeRehydrationSource.cs:10
- TeamMemberRecord.FirstName src/Organizations/AppointMe.Organizations/Employees/Database/TeamMemberRecord.cs:8
- TeamMemberRecord.LastName src/Organizations/AppointMe.Organizations/Employees/Database/TeamMemberRecord.cs:9
- TeamMemberDto.FullName src/Organizations/AppointMe.Organizations/Employees/TeamMemberDto.cs:6
- TeamMemberDto.FirstName src/Organizations/AppointMe.Organizations/Employees/TeamMemberDto.cs:7
- TeamMemberDto.LastName src/Organizations/AppointMe.Organizations/Employees/TeamMemberDto.cs:8
Email — 27 field(s)
- SuperAdminRegistry._emails src/AppointMe.Shared/Authentication/SuperAdminRegistry.cs:11
- UserIdentity.Email src/AppointMe.Shared/Authentication/UserIdentity.cs:6
- DemoUserOptions.Email src/AppointMe.Shared/Configuration/DemoOptions.cs:12
- Attendee.Email src/Booking/AppointMe.Booking/Attendees/Attendee.cs:10
- CustomerSnapshot.Email src/CRM/AppointMe.Crm.Contracts/Customers/CustomerSnapshot.cs:9
- CustomerRegisteredEvent.Email src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerRegisteredEvent.cs:11
- CustomerUpdatedEvent.Email src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerUpdatedEvent.cs:11
- Customer.Email src/CRM/AppointMe.Crm/Customers/Customer.cs:11
- CustomerDto.Email src/CRM/AppointMe.Crm/Customers/CustomerDto.cs:12
- CustomerRecord.Email src/CRM/AppointMe.Crm/Customers/Database/CustomerRecord.cs:10
- RegisterCustomerCommand.Email src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommand.cs:9
- RegisterCustomerRequest.Email src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerRequest.cs:9
- UpdateCustomerCommand.Email src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerCommand.cs:10
- UpdateCustomerRequest.Email src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerRequest.cs:9
- AuthenticatedUser.Email src/Identity/AppointMe.Identity.Contracts/Identity/AuthenticatedUser.cs:9
- SignupCommand.Email src/Identity/AppointMe.Identity/Signup/SignupCommand.cs:6
- SignupRequest.Email src/Identity/AppointMe.Identity/Signup/SignupRequest.cs:6
- User.Email src/Identity/AppointMe.Identity/Users/User.cs:11
- EmployeeInvitationResent.Email src/Organizations/AppointMe.Organizations.Contracts/Invitations/Events/EmployeeInvitationResent.cs:5
- EmployeeInvited.Email src/Organizations/AppointMe.Organizations.Contracts/Invitations/Events/EmployeeInvited.cs:5
- TeamMemberRecord.Email src/Organizations/AppointMe.Organizations/Employees/Database/TeamMemberRecord.cs:10
- Employee.Email src/Organizations/AppointMe.Organizations/Employees/Employee.cs:11
- TeamMemberDto.Email src/Organizations/AppointMe.Organizations/Employees/TeamMemberDto.cs:10
- EmployeeInvitation.Email src/Organizations/AppointMe.Organizations/Invitations/EmployeeInvitation.cs:10
- InviteEmployeeCommand.Email src/Organizations/AppointMe.Organizations/Invitations/InviteEmployee/InviteEmployeeCommand.cs:5
- InviteEmployeeRequest.Email src/Organizations/AppointMe.Organizations/Invitations/InviteEmployee/InviteEmployeeRequest.cs:5
- GetCurrentUserResponse.Email src/Organizations/AppointMe.Organizations/Me/GetCurrentUserResponse.cs:9
Date of birth — 11 field(s)
- Attendee.DateOfBirth src/Booking/AppointMe.Booking/Attendees/Attendee.cs:9
- CustomerSnapshot.DateOfBirth src/CRM/AppointMe.Crm.Contracts/Customers/CustomerSnapshot.cs:8
- CustomerRegisteredEvent.DateOfBirth src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerRegisteredEvent.cs:10
- CustomerUpdatedEvent.DateOfBirth src/CRM/AppointMe.Crm.Contracts/Customers/Events/CustomerUpdatedEvent.cs:10
- Customer.DateOfBirth src/CRM/AppointMe.Crm/Customers/Customer.cs:9
- CustomerDto.DateOfBirth src/CRM/AppointMe.Crm/Customers/CustomerDto.cs:10
- CustomerRecord.DateOfBirth src/CRM/AppointMe.Crm/Customers/Database/CustomerRecord.cs:8
- RegisterCustomerCommand.DateOfBirth src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerCommand.cs:7
- RegisterCustomerRequest.DateOfBirth src/CRM/AppointMe.Crm/Customers/RegisterCustomer/RegisterCustomerRequest.cs:7
- UpdateCustomerCommand.DateOfBirth src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerCommand.cs:8
- UpdateCustomerRequest.DateOfBirth src/CRM/AppointMe.Crm/Customers/UpdateCustomer/UpdateCustomerRequest.cs:7