Executive summary
dr-marek-jaskula/DomainDrivenDesignUniversity is rated At risk because critical security findings are open, most of them leaked passwords or keys. Its score is held back in part because ten passwords or keys sit in the current code. It scores 49 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step for the work it takes is updating the outdated dependencies, worth about 8 points. Replacing the ten exposed passwords or keys and switching the old ones off would lift Production Readiness itself, worth about 11 points. Raising Production Readiness to 70 would lift the score to about 59.
Twenty-three passwords or keys in the code's history and ten in the code are open to anyone who can read the repository. Thirteen known security holes in the packages the code depends on can be used by attackers, and eight settings leave the servers or containers unsafe. Replacing each exposed password or key, updating the vulnerable packages and correcting the unsafe settings would close these risks. Pinning each tool to an exact version would fix the five pipeline tools referenced by a changeable name. The seven loops of parts of the code that depend on each other need breaking by moving the shared parts into a project of their own.
The product code is 23,653 lines, about €47,000 to rebuild.
If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 49 to about 59.
New since the last survey: 5 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Outbox / dual-write · Dual write (no outbox): MimeKitEmailSender.SendEmailAsync src/Shopway.Infrastructure/Services/MimeKitEmailSender.cs
- Rich vs anemic model · Anemic entity: OrderLine src/Shopway.Domain/Orders/OrderLine.cs
- Rich vs anemic model · Anemic entity: Review src/Shopway.Domain/Products/Review.cs
Fixed since the last survey: 72 findings
- Cohesion (LCOM4) · Low cohesion: OrderHeadersController (LCOM4 8) src/Shopway.Presentation/Controllers/OrderHeaderController.Payment.cs
- Cohesion (LCOM4) · Low cohesion: OrderHeader (LCOM4 4) src/Shopway.Domain/Orders/OrderHeader.cs
- Dependency Hygiene · Vulnerable: MailKit
- Dependency Hygiene · Vulnerable: System.Linq.Dynamic.Core
- Dependency Hygiene · Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs
- Boundary Type-Coupling · Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/OrderHeader.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderHeader.cs
- Boundary Type-Coupling · Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/OrderHeader.cs
- Boundary Type-Coupling · Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/OrderHeader.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs
- Boundary Type-Coupling · Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Payment.cs
- Boundary Type-Coupling · Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/ValueObjects/ProductSummary.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/ValueObjects/ProductSummary.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderHeaderCreatedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderHeaderCreatedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Product.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Review.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Review.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ProductCreatedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ProductCreatedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs
- Boundary Type-Coupling · Cross-context type CustomerId (Shopway → Users) src/Shopway.Domain/Users/Customer.cs
- Boundary Type-Coupling · Cross-context type CustomerId (Shopway → Users) src/Shopway.Domain/Users/User.cs
- Change Coupling · Change coupling: IProductRepository.cs ↔ CachedOrderHeaderRepository.cs src/Shopway.Domain/Products/IProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: StartSessionAsync src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs
- Cancellation propagation · Async method without CancellationToken: Refund src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs
- Cancellation propagation · Async endpoint handler without CancellationToken: /publish-payment-result/success REDACTED
- Cancellation propagation · Async endpoint handler without CancellationToken: /publish-payment-result/failure REDACTED
- Cancellation propagation · Async method without CancellationToken: PublishMessage PaymentGateway/Webhook/WebhookService.cs
- Slice cohesion · Cross-slice coupling: Orders → Products src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandHandler.cs
- Slice cohesion · Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandUtilities.cs
- Slice cohesion · Cross-slice coupling: Orders → Products src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandValidator.cs
- Slice cohesion · Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs
- Slice cohesion · Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs
- Slice cohesion · Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs
- Slice cohesion · Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs
Rebuild cost: about €47,000 · Estimate
| Cost to rebuild | €16,000 to €78,000, for 260 to 822 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.7 at a score of 49. 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: 23,653 lines of product code, of which 45% is declarations and boilerplate, 39% straight logic and 15% logic with branches |
| 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Domain.Common.BaseTypes.Abstractions | 2 Domain.Common.DataProcessing.Abstractions | 3 Domain.Common.Results | 4 Domain.EntityKeys | 5 Domain.Common.BaseTypes | 6 Domain.Common.DataProcessing | 7 Domain.Common.Errors | 8 Domain.Common.DataProcessing.Proxy | 9 Domain.Products.ValueObjects | 10 Domain.Users.Authorization | 11 Domain.Users.ValueObjects | 12 Domain.Orders.ValueObjects | 13 Domain.Products | 14 Domain.Users | 15 Application.Abstractions | 16 Domain.Orders | 17 Domain.Products.DataProcessing.Filtering | 18 Domain.Products.DataProcessing.Sorting | 19 Application.Features | 20 Application.Features.Products.Queries | 21 Persistence.Framework | 22 Application.Features.Orders.Queries | 23 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery | 24 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery | 25 Application.Features.Products.Commands.BatchUpsertProduct | 26 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery | 27 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery | 28 Persistence.Repositories | 29 Application.Features.Proxy | 30 Application.Abstractions.CQRS | 31 Application.Features.Orders.Commands.CreateHeaderOrder | 32 Application.Features.Products.Commands.AddReview | 33 Application.Features.Products.Commands.RemoveReview | 34 Application.Features.Products.Queries.DynamicOffsetProductQuery | 35 Application.Features.Products.Queries.GetProductsCursorDictionary | 36 Application.Features.Products.Queries.GetProductsOffsetDictionary | 37 Application.Features.Products.Queries.QueryOffsetPageProduct | 38 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping | 39 Application.Mappings | 40 Presentation.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain.Common.BaseTypes.Abstractions | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain.Common.DataProcessing.Abstractions | 4 | |||||||||||||||||||||||||||||||||||||||
| 3 Domain.Common.Results | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 Domain.EntityKeys | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 Domain.Common.BaseTypes | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 Domain.Common.DataProcessing | 8 | |||||||||||||||||||||||||||||||||||||||
| 7 Domain.Common.Errors | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 8 Domain.Common.DataProcessing.Proxy | 12 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 9 Domain.Products.ValueObjects | 7 | 7 | 7 | |||||||||||||||||||||||||||||||||||||
| 10 Domain.Users.Authorization | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 11 Domain.Users.ValueObjects | 1 | 13 | 12 | 13 | ||||||||||||||||||||||||||||||||||||
| 12 Domain.Orders.ValueObjects | 2 | 4 | 2 | 4 | 4 | |||||||||||||||||||||||||||||||||||
| 13 Domain.Products | 2 | 6 | 1 | 2 | 1 | 9 | 1 | |||||||||||||||||||||||||||||||||
| 14 Domain.Users | 3 | 2 | 1 | 13 | ||||||||||||||||||||||||||||||||||||
| 15 Application.Abstractions | 4 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 16 Domain.Orders | 5 | 6 | 3 | 3 | 1 | 6 | 2 | |||||||||||||||||||||||||||||||||
| 17 Domain.Products.DataProcessing.Filtering | 8 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 18 Domain.Products.DataProcessing.Sorting | 4 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 19 Application.Features | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 20 Application.Features.Products.Queries | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 Persistence.Framework | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Application.Features.Orders.Queries | 2 | 1 | 4 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 23 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 24 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 25 Application.Features.Products.Commands.BatchUpsertProduct | 1 | 5 | 4 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 26 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 27 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 28 Persistence.Repositories | 1 | 8 | 1 | 1 | 2 | 1 | 3 | 2 | 2 | 5 | 2 | 7 | ||||||||||||||||||||||||||||
| 29 Application.Features.Proxy | 2 | 1 | 1 | 8 | 1 | 2 | 1 | 4 | 1 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||
| 30 Application.Abstractions.CQRS | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Application.Features.Orders.Commands.CreateHeaderOrder | 2 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 32 Application.Features.Products.Commands.AddReview | 1 | 3 | 1 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 33 Application.Features.Products.Commands.RemoveReview | 2 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 34 Application.Features.Products.Queries.DynamicOffsetProductQuery | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 35 Application.Features.Products.Queries.GetProductsCursorDictionary | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||
| 36 Application.Features.Products.Queries.GetProductsOffsetDictionary | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||
| 37 Application.Features.Products.Queries.QueryOffsetPageProduct | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 38 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 39 Application.Mappings | 1 | 2 | 2 | 2 | 1 | 4 | 3 | 2 | 4 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 40 Presentation.Controllers | 1 | 1 | 5 | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 |
2→6 Domain.Common.DataProcessing.Abstractions uses Domain.Common.DataProcessing part of a loop✕
- Connections
- 4 pairs of types, where a type in Domain.Common.DataProcessing.Abstractions uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilter→Shopway.Domain.Common.DataProcessing.FilterByEntryShopway.Domain.Common.DataProcessing.Abstractions.IDynamicMapping→Shopway.Domain.Common.DataProcessing.MappingEntryShopway.Domain.Common.DataProcessing.Abstractions.IDynamicSortBy→Shopway.Domain.Common.DataProcessing.SortByEntryShopway.Domain.Common.DataProcessing.Abstractions.ILikeProvider→Shopway.Domain.Common.DataProcessing.LikeEntry
- Direction
- Domain.Common.DataProcessing.Abstractions uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Common.DataProcessing.Abstractions, while a change to Domain.Common.DataProcessing.Abstractions can't break Domain.Common.DataProcessing.
- 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.
3→7 Domain.Common.Results uses Domain.Common.Errors part of a loop✕
- Connections
- 2 pairs of types, where a type in Domain.Common.Results uses a type in Domain.Common.Errors.
- The types involved
Shopway.Domain.Common.Results.Result→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Common.Results.ValidationResult→Shopway.Domain.Common.Errors.Error
- Direction
- Domain.Common.Results uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Domain.Common.Results, while a change to Domain.Common.Results can't break Domain.Common.Errors.
- 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.
4→1 Domain.EntityKeys uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.EntityKeys uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.EntityKeys.ProductKey→Shopway.Domain.Common.BaseTypes.Abstractions.IUniqueKeyShopway.Domain.EntityKeys.ReviewKey→Shopway.Domain.Common.BaseTypes.Abstractions.IUniqueKey
- Direction
- Domain.EntityKeys uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.EntityKeys, while a change to Domain.EntityKeys can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.EntityKeys uses a module listed above it, which is the healthy direction.
4→13 Domain.EntityKeys uses Domain.Products part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.EntityKeys uses a type in Domain.Products.
- The types involved
Shopway.Domain.EntityKeys.ProductKey→Shopway.Domain.Products.Product
- Direction
- Domain.EntityKeys uses Domain.Products, so a change to Domain.Products can break Domain.EntityKeys, while a change to Domain.EntityKeys can't break Domain.Products.
- 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.
5→1 Domain.Common.BaseTypes uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 5 pairs of types, where a type in Domain.Common.BaseTypes uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Common.BaseTypes.AggregateRoot→Shopway.Domain.Common.BaseTypes.Abstractions.IAggregateRootShopway.Domain.Common.BaseTypes.AggregateRoot→Shopway.Domain.Common.BaseTypes.Abstractions.IDomainEventShopway.Domain.Common.BaseTypes.DomainEvent→Shopway.Domain.Common.BaseTypes.Abstractions.IDomainEventShopway.Domain.Common.BaseTypes.Entity→Shopway.Domain.Common.BaseTypes.Abstractions.IEntityShopway.Domain.Common.BaseTypes.ValueObject→Shopway.Domain.Common.BaseTypes.Abstractions.IValueObject
- Direction
- Domain.Common.BaseTypes uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Common.BaseTypes, while a change to Domain.Common.BaseTypes can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Common.BaseTypes uses a module listed above it, which is the healthy direction.
5→3 Domain.Common.BaseTypes uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Domain.Common.BaseTypes uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Common.BaseTypes.IEntityUtilities→Shopway.Domain.Common.Results.Result
- Direction
- Domain.Common.BaseTypes uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Common.BaseTypes, while a change to Domain.Common.BaseTypes can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Common.BaseTypes uses a module listed above it, which is the healthy direction.
6→2 Domain.Common.DataProcessing uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 8 pairs of types, where a type in Domain.Common.DataProcessing uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Common.DataProcessing.CursorPage→Shopway.Domain.Common.DataProcessing.Abstractions.ICursorPageShopway.Domain.Common.DataProcessing.DataTransferObject→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursorShopway.Domain.Common.DataProcessing.IncludeBuilder→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Common.DataProcessing.IncludeBuilder→Shopway.Domain.Common.DataProcessing.Abstractions.IThenIncludeBuilderShopway.Domain.Common.DataProcessing.IncludeBuilderOrchestrator→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Common.DataProcessing.IncludeBuilderOrchestrator→Shopway.Domain.Common.DataProcessing.Abstractions.IThenIncludeBuilderShopway.Domain.Common.DataProcessing.OffsetPage→Shopway.Domain.Common.DataProcessing.Abstractions.IOffsetPageShopway.Domain.Common.DataProcessing.ThenIncludeBuilder→Shopway.Domain.Common.DataProcessing.Abstractions.IThenIncludeBuilder
- Direction
- Domain.Common.DataProcessing uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Common.DataProcessing, while a change to Domain.Common.DataProcessing can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Common.DataProcessing uses a module listed above it, which is the healthy direction.
7→1 Domain.Common.Errors uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.Common.Errors uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Common.Errors.Error→Shopway.Domain.Common.BaseTypes.Abstractions.IEntityIdShopway.Domain.Common.Errors.Error→Shopway.Domain.Common.BaseTypes.Abstractions.IUniqueKey
- Direction
- Domain.Common.Errors uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Common.Errors, while a change to Domain.Common.Errors can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Common.Errors uses a module listed above it, which is the healthy direction.
7→3 Domain.Common.Errors uses Domain.Common.Results✕
- Connections
- 3 pairs of types, where a type in Domain.Common.Errors uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Common.Errors.Error→Shopway.Domain.Common.Results.ResultShopway.Domain.Common.Errors.Error→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Common.Errors.ErrorUtilities→Shopway.Domain.Common.Results.ValidationResult
- Direction
- Domain.Common.Errors uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Common.Errors, while a change to Domain.Common.Errors can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Common.Errors uses a module listed above it, which is the healthy direction.
8→2 Domain.Common.DataProcessing.Proxy uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 12 pairs of types, where a type in Domain.Common.DataProcessing.Proxy uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Common.DataProcessing.Proxy.DynamicFilter→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilterShopway.Domain.Common.DataProcessing.Proxy.DynamicMapping→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicMappingShopway.Domain.Common.DataProcessing.Proxy.DynamicSortBy→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicSortByShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ICursorPageShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMappingShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IOffsetPageShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ISortByShopway.Domain.Common.DataProcessing.Proxy.IProxyWithKeyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Common.DataProcessing.Proxy.IProxyWithKeyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMappingShopway.Domain.Common.DataProcessing.Proxy.OffsetOrCursorPage→Shopway.Domain.Common.DataProcessing.Abstractions.IPage
- Direction
- Domain.Common.DataProcessing.Proxy uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Common.DataProcessing.Proxy, while a change to Domain.Common.DataProcessing.Proxy can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Common.DataProcessing.Proxy uses a module listed above it, which is the healthy direction.
8→3 Domain.Common.DataProcessing.Proxy uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Domain.Common.DataProcessing.Proxy uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Common.DataProcessing.Proxy.OffsetOrCursorPage→Shopway.Domain.Common.Results.Result
- Direction
- Domain.Common.DataProcessing.Proxy uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Common.DataProcessing.Proxy, while a change to Domain.Common.DataProcessing.Proxy can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Common.DataProcessing.Proxy uses a module listed above it, which is the healthy direction.
8→6 Domain.Common.DataProcessing.Proxy uses Domain.Common.DataProcessing✕
- Connections
- 6 pairs of types, where a type in Domain.Common.DataProcessing.Proxy uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Common.DataProcessing.Proxy.DynamicFilter→Shopway.Domain.Common.DataProcessing.FilterByEntryShopway.Domain.Common.DataProcessing.Proxy.DynamicMapping→Shopway.Domain.Common.DataProcessing.MappingEntryShopway.Domain.Common.DataProcessing.Proxy.DynamicSortBy→Shopway.Domain.Common.DataProcessing.SortByEntryShopway.Domain.Common.DataProcessing.Proxy.IProxyRepository→Shopway.Domain.Common.DataProcessing.LikeEntryShopway.Domain.Common.DataProcessing.Proxy.OffsetOrCursorPage→Shopway.Domain.Common.DataProcessing.CursorPageShopway.Domain.Common.DataProcessing.Proxy.OffsetOrCursorPage→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Domain.Common.DataProcessing.Proxy uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Common.DataProcessing.Proxy, while a change to Domain.Common.DataProcessing.Proxy can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Domain.Common.DataProcessing.Proxy uses a module listed above it, which is the healthy direction.
9→3 Domain.Products.ValueObjects uses Domain.Common.Results✕
- Connections
- 7 pairs of types, where a type in Domain.Products.ValueObjects uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Products.ValueObjects.Description→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.Price→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.ProductName→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.Revision→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.Stars→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.Title→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Products.ValueObjects.UomCode→Shopway.Domain.Common.Results.ValidationResult
- Direction
- Domain.Products.ValueObjects uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Products.ValueObjects, while a change to Domain.Products.ValueObjects can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Products.ValueObjects uses a module listed above it, which is the healthy direction.
9→5 Domain.Products.ValueObjects uses Domain.Common.BaseTypes✕
- Connections
- 7 pairs of types, where a type in Domain.Products.ValueObjects uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Products.ValueObjects.Description→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.Price→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.ProductName→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.Revision→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.Stars→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.Title→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Products.ValueObjects.UomCode→Shopway.Domain.Common.BaseTypes.ValueObject
- Direction
- Domain.Products.ValueObjects uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Products.ValueObjects, while a change to Domain.Products.ValueObjects can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Products.ValueObjects uses a module listed above it, which is the healthy direction.
9→7 Domain.Products.ValueObjects uses Domain.Common.Errors✕
- Connections
- 7 pairs of types, where a type in Domain.Products.ValueObjects uses a type in Domain.Common.Errors.
- The types involved
Shopway.Domain.Products.ValueObjects.Description→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.Price→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.ProductName→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.Revision→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.Stars→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.Title→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Products.ValueObjects.UomCode→Shopway.Domain.Common.Errors.Error
- Direction
- Domain.Products.ValueObjects uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Domain.Products.ValueObjects, while a change to Domain.Products.ValueObjects can't break Domain.Common.Errors.
- Position
- Below the diagonal: Domain.Products.ValueObjects uses a module listed above it, which is the healthy direction.
10→3 Domain.Users.Authorization uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Domain.Users.Authorization uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Users.Authorization.Permission→Shopway.Domain.Common.Results.Result
- Direction
- Domain.Users.Authorization uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Users.Authorization, while a change to Domain.Users.Authorization can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Users.Authorization uses a module listed above it, which is the healthy direction.
10→7 Domain.Users.Authorization uses Domain.Common.Errors✕
- Connections
- 1 pair of types, where a type in Domain.Users.Authorization uses a type in Domain.Common.Errors.
- The types involved
Shopway.Domain.Users.Authorization.Permission→Shopway.Domain.Common.Errors.Error
- Direction
- Domain.Users.Authorization uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Domain.Users.Authorization, while a change to Domain.Users.Authorization can't break Domain.Common.Errors.
- Position
- Below the diagonal: Domain.Users.Authorization uses a module listed above it, which is the healthy direction.
10→14 Domain.Users.Authorization uses Domain.Users part of a loop✕
- Connections
- 3 pairs of types, where a type in Domain.Users.Authorization uses a type in Domain.Users.
- The types involved
Shopway.Domain.Users.Authorization.IAuthorizationRepository→Shopway.Domain.Users.UserIdShopway.Domain.Users.Authorization.Role→Shopway.Domain.Users.UserShopway.Domain.Users.Authorization.RoleUser→Shopway.Domain.Users.UserId
- Direction
- Domain.Users.Authorization uses Domain.Users, so a change to Domain.Users can break Domain.Users.Authorization, while a change to Domain.Users.Authorization can't break Domain.Users.
- 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.
11→1 Domain.Users.ValueObjects uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 1 pair of types, where a type in Domain.Users.ValueObjects uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Users.ValueObjects.Address→Shopway.Domain.Common.BaseTypes.Abstractions.IValueObject
- Direction
- Domain.Users.ValueObjects uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Users.ValueObjects, while a change to Domain.Users.ValueObjects can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Users.ValueObjects uses a module listed above it, which is the healthy direction.
11→3 Domain.Users.ValueObjects uses Domain.Common.Results✕
- Connections
- 13 pairs of types, where a type in Domain.Users.ValueObjects uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Users.ValueObjects.AccessToken→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.Address→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.Email→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.ExternalIdentityProvider→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.FirstName→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.LastName→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.Password→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.PasswordHash→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.PhoneNumber→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.RefreshToken→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.TwoFactorTokenHash→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.TwoFactorToptSecret→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Users.ValueObjects.Username→Shopway.Domain.Common.Results.ValidationResult
- Direction
- Domain.Users.ValueObjects uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Users.ValueObjects, while a change to Domain.Users.ValueObjects can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Users.ValueObjects uses a module listed above it, which is the healthy direction.
11→5 Domain.Users.ValueObjects uses Domain.Common.BaseTypes✕
- Connections
- 12 pairs of types, where a type in Domain.Users.ValueObjects uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Users.ValueObjects.AccessToken→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.Email→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.ExternalIdentityProvider→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.FirstName→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.LastName→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.Password→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.PasswordHash→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.PhoneNumber→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.RefreshToken→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.TwoFactorTokenHash→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.TwoFactorToptSecret→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Users.ValueObjects.Username→Shopway.Domain.Common.BaseTypes.ValueObject
- Direction
- Domain.Users.ValueObjects uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Users.ValueObjects, while a change to Domain.Users.ValueObjects can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Users.ValueObjects uses a module listed above it, which is the healthy direction.
11→7 Domain.Users.ValueObjects uses Domain.Common.Errors✕
- Connections
- 13 pairs of types, where a type in Domain.Users.ValueObjects uses a type in Domain.Common.Errors.
- The types involved
Shopway.Domain.Users.ValueObjects.AccessToken→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.Address→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.Email→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.ExternalIdentityProvider→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.FirstName→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.LastName→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.Password→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.PasswordHash→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.PhoneNumber→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.RefreshToken→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.TwoFactorTokenHash→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.TwoFactorToptSecret→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Users.ValueObjects.Username→Shopway.Domain.Common.Errors.Error
- Direction
- Domain.Users.ValueObjects uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Domain.Users.ValueObjects, while a change to Domain.Users.ValueObjects can't break Domain.Common.Errors.
- Position
- Below the diagonal: Domain.Users.ValueObjects uses a module listed above it, which is the healthy direction.
12→1 Domain.Orders.ValueObjects uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.Orders.ValueObjects uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Common.BaseTypes.Abstractions.IValueObjectShopway.Domain.Orders.ValueObjects.Session→Shopway.Domain.Common.BaseTypes.Abstractions.IValueObject
- Direction
- Domain.Orders.ValueObjects uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Orders.ValueObjects, while a change to Domain.Orders.ValueObjects can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Orders.ValueObjects uses a module listed above it, which is the healthy direction.
12→3 Domain.Orders.ValueObjects uses Domain.Common.Results✕
- Connections
- 4 pairs of types, where a type in Domain.Orders.ValueObjects uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Orders.ValueObjects.Amount→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Orders.ValueObjects.Discount→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Common.Results.ValidationResultShopway.Domain.Orders.ValueObjects.Session→Shopway.Domain.Common.Results.ValidationResult
- Direction
- Domain.Orders.ValueObjects uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Orders.ValueObjects, while a change to Domain.Orders.ValueObjects can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Orders.ValueObjects uses a module listed above it, which is the healthy direction.
12→5 Domain.Orders.ValueObjects uses Domain.Common.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Domain.Orders.ValueObjects uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Orders.ValueObjects.Amount→Shopway.Domain.Common.BaseTypes.ValueObjectShopway.Domain.Orders.ValueObjects.Discount→Shopway.Domain.Common.BaseTypes.ValueObject
- Direction
- Domain.Orders.ValueObjects uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Orders.ValueObjects, while a change to Domain.Orders.ValueObjects can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Orders.ValueObjects uses a module listed above it, which is the healthy direction.
12→7 Domain.Orders.ValueObjects uses Domain.Common.Errors✕
- Connections
- 4 pairs of types, where a type in Domain.Orders.ValueObjects uses a type in Domain.Common.Errors.
- The types involved
Shopway.Domain.Orders.ValueObjects.Amount→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Orders.ValueObjects.Discount→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Common.Errors.ErrorShopway.Domain.Orders.ValueObjects.Session→Shopway.Domain.Common.Errors.Error
- Direction
- Domain.Orders.ValueObjects uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Domain.Orders.ValueObjects, while a change to Domain.Orders.ValueObjects can't break Domain.Common.Errors.
- Position
- Below the diagonal: Domain.Orders.ValueObjects uses a module listed above it, which is the healthy direction.
12→9 Domain.Orders.ValueObjects uses Domain.Products.ValueObjects✕
- Connections
- 4 pairs of types, where a type in Domain.Orders.ValueObjects uses a type in Domain.Products.ValueObjects.
- The types involved
Shopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Products.ValueObjects.PriceShopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Products.ValueObjects.ProductNameShopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Products.ValueObjects.RevisionShopway.Domain.Orders.ValueObjects.ProductSummary→Shopway.Domain.Products.ValueObjects.UomCode
- Direction
- Domain.Orders.ValueObjects uses Domain.Products.ValueObjects, so a change to Domain.Products.ValueObjects can break Domain.Orders.ValueObjects, while a change to Domain.Orders.ValueObjects can't break Domain.Products.ValueObjects.
- Position
- Below the diagonal: Domain.Orders.ValueObjects uses a module listed above it, which is the healthy direction.
13→1 Domain.Products uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.Products uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Products.Product→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditableShopway.Domain.Products.Review→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditable
- Direction
- Domain.Products uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Products, while a change to Domain.Products can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→2 Domain.Products uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 6 pairs of types, where a type in Domain.Products uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ICursorPageShopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMappingShopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IOffsetPageShopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ISortBy
- Direction
- Domain.Products uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Products, while a change to Domain.Products can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→4 Domain.Products uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Domain.Products uses a type in Domain.EntityKeys.
- The types involved
Shopway.Domain.Products.IProductRepository→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Domain.Products uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Domain.Products, while a change to Domain.Products can't break Domain.EntityKeys.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→5 Domain.Products uses Domain.Common.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Domain.Products uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Products.Product→Shopway.Domain.Common.BaseTypes.AggregateRootShopway.Domain.Products.Review→Shopway.Domain.Common.BaseTypes.Entity
- Direction
- Domain.Products uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Products, while a change to Domain.Products can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→6 Domain.Products uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Domain.Products uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Products.IProductRepository→Shopway.Domain.Common.DataProcessing.LikeEntry
- Direction
- Domain.Products uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Products, while a change to Domain.Products can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→9 Domain.Products uses Domain.Products.ValueObjects✕
- Connections
- 9 pairs of types, where a type in Domain.Products uses a type in Domain.Products.ValueObjects.
- The types involved
Shopway.Domain.Products.IProductRepository→Shopway.Domain.Products.ValueObjects.TitleShopway.Domain.Products.Product→Shopway.Domain.Products.ValueObjects.PriceShopway.Domain.Products.Product→Shopway.Domain.Products.ValueObjects.ProductNameShopway.Domain.Products.Product→Shopway.Domain.Products.ValueObjects.RevisionShopway.Domain.Products.Product→Shopway.Domain.Products.ValueObjects.TitleShopway.Domain.Products.Product→Shopway.Domain.Products.ValueObjects.UomCodeShopway.Domain.Products.Review→Shopway.Domain.Products.ValueObjects.DescriptionShopway.Domain.Products.Review→Shopway.Domain.Products.ValueObjects.StarsShopway.Domain.Products.Review→Shopway.Domain.Products.ValueObjects.Title
- Direction
- Domain.Products uses Domain.Products.ValueObjects, so a change to Domain.Products.ValueObjects can break Domain.Products, while a change to Domain.Products can't break Domain.Products.ValueObjects.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
13→11 Domain.Products uses Domain.Users.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.Products uses a type in Domain.Users.ValueObjects.
- The types involved
Shopway.Domain.Products.Review→Shopway.Domain.Users.ValueObjects.Username
- Direction
- Domain.Products uses Domain.Users.ValueObjects, so a change to Domain.Users.ValueObjects can break Domain.Products, while a change to Domain.Products can't break Domain.Users.ValueObjects.
- Position
- Below the diagonal: Domain.Products uses a module listed above it, which is the healthy direction.
14→1 Domain.Users uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 3 pairs of types, where a type in Domain.Users uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Users.Customer→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditableShopway.Domain.Users.User→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditableShopway.Domain.Users.UserId→Shopway.Domain.Common.BaseTypes.Abstractions.IEntityId
- Direction
- Domain.Users uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Users, while a change to Domain.Users can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Users uses a module listed above it, which is the healthy direction.
14→5 Domain.Users uses Domain.Common.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Domain.Users uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Users.Customer→Shopway.Domain.Common.BaseTypes.EntityShopway.Domain.Users.User→Shopway.Domain.Common.BaseTypes.AggregateRoot
- Direction
- Domain.Users uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Users, while a change to Domain.Users can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Users uses a module listed above it, which is the healthy direction.
14→10 Domain.Users uses Domain.Users.Authorization✕
- Connections
- 1 pair of types, where a type in Domain.Users uses a type in Domain.Users.Authorization.
- The types involved
Shopway.Domain.Users.User→Shopway.Domain.Users.Authorization.Role
- Direction
- Domain.Users uses Domain.Users.Authorization, so a change to Domain.Users.Authorization can break Domain.Users, while a change to Domain.Users can't break Domain.Users.Authorization.
- Position
- Below the diagonal: Domain.Users uses a module listed above it, which is the healthy direction.
14→11 Domain.Users uses Domain.Users.ValueObjects✕
- Connections
- 13 pairs of types, where a type in Domain.Users uses a type in Domain.Users.ValueObjects.
- The types involved
Shopway.Domain.Users.Customer→Shopway.Domain.Users.ValueObjects.AddressShopway.Domain.Users.Customer→Shopway.Domain.Users.ValueObjects.FirstNameShopway.Domain.Users.Customer→Shopway.Domain.Users.ValueObjects.LastNameShopway.Domain.Users.Customer→Shopway.Domain.Users.ValueObjects.PhoneNumberShopway.Domain.Users.IUserRepository→Shopway.Domain.Users.ValueObjects.EmailShopway.Domain.Users.IUserRepository→Shopway.Domain.Users.ValueObjects.UsernameShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.EmailShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.ExternalIdentityProviderShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.PasswordHashShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.RefreshTokenShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.TwoFactorTokenHashShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.TwoFactorToptSecretShopway.Domain.Users.User→Shopway.Domain.Users.ValueObjects.Username
- Direction
- Domain.Users uses Domain.Users.ValueObjects, so a change to Domain.Users.ValueObjects can break Domain.Users, while a change to Domain.Users can't break Domain.Users.ValueObjects.
- Position
- Below the diagonal: Domain.Users uses a module listed above it, which is the healthy direction.
15→3 Application.Abstractions uses Domain.Common.Results✕
- Connections
- 4 pairs of types, where a type in Application.Abstractions uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Abstractions.IFuzzySearch→Shopway.Domain.Common.Results.ResultShopway.Application.Abstractions.ISecurityTokenService→Shopway.Domain.Common.Results.ResultShopway.Application.Abstractions.IValidator→Shopway.Domain.Common.Results.ResultShopway.Application.Abstractions.IValidator→Shopway.Domain.Common.Results.ValidationResult
- Direction
- Application.Abstractions uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Abstractions, while a change to Application.Abstractions can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Abstractions uses a module listed above it, which is the healthy direction.
15→7 Application.Abstractions uses Domain.Common.Errors✕
- Connections
- 1 pair of types, where a type in Application.Abstractions uses a type in Domain.Common.Errors.
- The types involved
Shopway.Application.Abstractions.IValidator→Shopway.Domain.Common.Errors.Error
- Direction
- Application.Abstractions uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Application.Abstractions, while a change to Application.Abstractions can't break Domain.Common.Errors.
- Position
- Below the diagonal: Application.Abstractions uses a module listed above it, which is the healthy direction.
15→11 Application.Abstractions uses Domain.Users.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Application.Abstractions uses a type in Domain.Users.ValueObjects.
- The types involved
Shopway.Application.Abstractions.ISecurityTokenService→Shopway.Domain.Users.ValueObjects.EmailShopway.Application.Abstractions.ISecurityTokenService→Shopway.Domain.Users.ValueObjects.Username
- Direction
- Application.Abstractions uses Domain.Users.ValueObjects, so a change to Domain.Users.ValueObjects can break Application.Abstractions, while a change to Application.Abstractions can't break Domain.Users.ValueObjects.
- Position
- Below the diagonal: Application.Abstractions uses a module listed above it, which is the healthy direction.
15→14 Application.Abstractions uses Domain.Users✕
- Connections
- 2 pairs of types, where a type in Application.Abstractions uses a type in Domain.Users.
- The types involved
Shopway.Application.Abstractions.ISecurityTokenService→Shopway.Domain.Users.UserShopway.Application.Abstractions.IUserContextService→Shopway.Domain.Users.UserId
- Direction
- Application.Abstractions uses Domain.Users, so a change to Domain.Users can break Application.Abstractions, while a change to Application.Abstractions can't break Domain.Users.
- Position
- Below the diagonal: Application.Abstractions uses a module listed above it, which is the healthy direction.
16→1 Domain.Orders uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 5 pairs of types, where a type in Domain.Orders uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Domain.Orders.OrderHeader→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditableShopway.Domain.Orders.OrderHeader→Shopway.Domain.Common.BaseTypes.Abstractions.ISoftDeletableShopway.Domain.Orders.OrderLine→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditableShopway.Domain.Orders.OrderLineKey→Shopway.Domain.Common.BaseTypes.Abstractions.IUniqueKeyShopway.Domain.Orders.Payment→Shopway.Domain.Common.BaseTypes.Abstractions.IAuditable
- Direction
- Domain.Orders uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Domain.Orders, while a change to Domain.Orders can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→2 Domain.Orders uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 6 pairs of types, where a type in Domain.Orders uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ICursorPageShopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMappingShopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IOffsetPageShopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ISortBy
- Direction
- Domain.Orders uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Orders, while a change to Domain.Orders can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→3 Domain.Orders uses Domain.Common.Results✕
- Connections
- 3 pairs of types, where a type in Domain.Orders uses a type in Domain.Common.Results.
- The types involved
Shopway.Domain.Orders.IPaymentGatewayService→Shopway.Domain.Common.Results.ResultShopway.Domain.Orders.OrderHeader→Shopway.Domain.Common.Results.ResultShopway.Domain.Orders.Payment→Shopway.Domain.Common.Results.Result
- Direction
- Domain.Orders uses Domain.Common.Results, so a change to Domain.Common.Results can break Domain.Orders, while a change to Domain.Orders can't break Domain.Common.Results.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→5 Domain.Orders uses Domain.Common.BaseTypes✕
- Connections
- 3 pairs of types, where a type in Domain.Orders uses a type in Domain.Common.BaseTypes.
- The types involved
Shopway.Domain.Orders.OrderHeader→Shopway.Domain.Common.BaseTypes.AggregateRootShopway.Domain.Orders.OrderLine→Shopway.Domain.Common.BaseTypes.EntityShopway.Domain.Orders.Payment→Shopway.Domain.Common.BaseTypes.Entity
- Direction
- Domain.Orders uses Domain.Common.BaseTypes, so a change to Domain.Common.BaseTypes can break Domain.Orders, while a change to Domain.Orders can't break Domain.Common.BaseTypes.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→6 Domain.Orders uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Domain.Orders uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Common.DataProcessing.LikeEntry
- Direction
- Domain.Orders uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Orders, while a change to Domain.Orders can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→12 Domain.Orders uses Domain.Orders.ValueObjects✕
- Connections
- 6 pairs of types, where a type in Domain.Orders uses a type in Domain.Orders.ValueObjects.
- The types involved
Shopway.Domain.Orders.IPaymentGatewayService→Shopway.Domain.Orders.ValueObjects.SessionShopway.Domain.Orders.OrderHeader→Shopway.Domain.Orders.ValueObjects.DiscountShopway.Domain.Orders.OrderLine→Shopway.Domain.Orders.ValueObjects.AmountShopway.Domain.Orders.OrderLine→Shopway.Domain.Orders.ValueObjects.DiscountShopway.Domain.Orders.OrderLine→Shopway.Domain.Orders.ValueObjects.ProductSummaryShopway.Domain.Orders.Payment→Shopway.Domain.Orders.ValueObjects.Session
- Direction
- Domain.Orders uses Domain.Orders.ValueObjects, so a change to Domain.Orders.ValueObjects can break Domain.Orders, while a change to Domain.Orders can't break Domain.Orders.ValueObjects.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
16→14 Domain.Orders uses Domain.Users✕
- Connections
- 2 pairs of types, where a type in Domain.Orders uses a type in Domain.Users.
- The types involved
Shopway.Domain.Orders.IOrderHeaderRepository→Shopway.Domain.Users.UserIdShopway.Domain.Orders.OrderHeader→Shopway.Domain.Users.UserId
- Direction
- Domain.Orders uses Domain.Users, so a change to Domain.Users can break Domain.Orders, while a change to Domain.Orders can't break Domain.Users.
- Position
- Below the diagonal: Domain.Orders uses a module listed above it, which is the healthy direction.
17→2 Domain.Products.DataProcessing.Filtering uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 8 pairs of types, where a type in Domain.Products.DataProcessing.Filtering uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Products.DataProcessing.Filtering.ProductDictionaryStaticFilter→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Products.DataProcessing.Filtering.ProductDictionaryStaticFilter→Shopway.Domain.Common.DataProcessing.Abstractions.ILikeProviderShopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilterShopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter→Shopway.Domain.Common.DataProcessing.Abstractions.ILikeProviderShopway.Domain.Products.DataProcessing.Filtering.ProductFuzzyFilter→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Products.DataProcessing.Filtering.ProductFuzzyFilter→Shopway.Domain.Common.DataProcessing.Abstractions.ILikeProviderShopway.Domain.Products.DataProcessing.Filtering.ProductStaticFilter→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Domain.Products.DataProcessing.Filtering.ProductStaticFilter→Shopway.Domain.Common.DataProcessing.Abstractions.ILikeProvider
- Direction
- Domain.Products.DataProcessing.Filtering uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Products.DataProcessing.Filtering, while a change to Domain.Products.DataProcessing.Filtering can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Filtering uses a module listed above it, which is the healthy direction.
17→6 Domain.Products.DataProcessing.Filtering uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Domain.Products.DataProcessing.Filtering uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter→Shopway.Domain.Common.DataProcessing.FilterByEntry
- Direction
- Domain.Products.DataProcessing.Filtering uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Products.DataProcessing.Filtering, while a change to Domain.Products.DataProcessing.Filtering can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Filtering uses a module listed above it, which is the healthy direction.
17→13 Domain.Products.DataProcessing.Filtering uses Domain.Products✕
- Connections
- 4 pairs of types, where a type in Domain.Products.DataProcessing.Filtering uses a type in Domain.Products.
- The types involved
Shopway.Domain.Products.DataProcessing.Filtering.ProductDictionaryStaticFilter→Shopway.Domain.Products.ProductShopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter→Shopway.Domain.Products.ProductShopway.Domain.Products.DataProcessing.Filtering.ProductFuzzyFilter→Shopway.Domain.Products.ProductShopway.Domain.Products.DataProcessing.Filtering.ProductStaticFilter→Shopway.Domain.Products.Product
- Direction
- Domain.Products.DataProcessing.Filtering uses Domain.Products, so a change to Domain.Products can break Domain.Products.DataProcessing.Filtering, while a change to Domain.Products.DataProcessing.Filtering can't break Domain.Products.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Filtering uses a module listed above it, which is the healthy direction.
18→2 Domain.Products.DataProcessing.Sorting uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 4 pairs of types, where a type in Domain.Products.DataProcessing.Sorting uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Domain.Products.DataProcessing.Sorting.CommonProductSortBy→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicSortByShopway.Domain.Products.DataProcessing.Sorting.CommonProductSortBy→Shopway.Domain.Common.DataProcessing.Abstractions.ISortByShopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy→Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicSortByShopway.Domain.Products.DataProcessing.Sorting.ProductStaticSortBy→Shopway.Domain.Common.DataProcessing.Abstractions.ISortBy
- Direction
- Domain.Products.DataProcessing.Sorting uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Domain.Products.DataProcessing.Sorting, while a change to Domain.Products.DataProcessing.Sorting can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Sorting uses a module listed above it, which is the healthy direction.
18→6 Domain.Products.DataProcessing.Sorting uses Domain.Common.DataProcessing✕
- Connections
- 2 pairs of types, where a type in Domain.Products.DataProcessing.Sorting uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Domain.Products.DataProcessing.Sorting.CommonProductSortBy→Shopway.Domain.Common.DataProcessing.SortByEntryShopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy→Shopway.Domain.Common.DataProcessing.SortByEntry
- Direction
- Domain.Products.DataProcessing.Sorting uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Domain.Products.DataProcessing.Sorting, while a change to Domain.Products.DataProcessing.Sorting can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Sorting uses a module listed above it, which is the healthy direction.
18→13 Domain.Products.DataProcessing.Sorting uses Domain.Products✕
- Connections
- 3 pairs of types, where a type in Domain.Products.DataProcessing.Sorting uses a type in Domain.Products.
- The types involved
Shopway.Domain.Products.DataProcessing.Sorting.CommonProductSortBy→Shopway.Domain.Products.ProductShopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy→Shopway.Domain.Products.ProductShopway.Domain.Products.DataProcessing.Sorting.ProductStaticSortBy→Shopway.Domain.Products.Product
- Direction
- Domain.Products.DataProcessing.Sorting uses Domain.Products, so a change to Domain.Products can break Domain.Products.DataProcessing.Sorting, while a change to Domain.Products.DataProcessing.Sorting can't break Domain.Products.
- Position
- Below the diagonal: Domain.Products.DataProcessing.Sorting uses a module listed above it, which is the healthy direction.
19→2 Application.Features uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 2 pairs of types, where a type in Application.Features uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Application.Features.DataTransferObjectResponse→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursorShopway.Application.Features.DictionaryResponseEntry→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursor
- Direction
- Application.Features uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Application.Features, while a change to Application.Features can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Application.Features uses a module listed above it, which is the healthy direction.
19→6 Application.Features uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.DataTransferObjectResponse→Shopway.Domain.Common.DataProcessing.DataTransferObject
- Direction
- Application.Features uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features, while a change to Application.Features can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features uses a module listed above it, which is the healthy direction.
19→7 Application.Features uses Domain.Common.Errors✕
- Connections
- 1 pair of types, where a type in Application.Features uses a type in Domain.Common.Errors.
- The types involved
Shopway.Application.Features.BatchResponseEntry→Shopway.Domain.Common.Errors.Error
- Direction
- Application.Features uses Domain.Common.Errors, so a change to Domain.Common.Errors can break Application.Features, while a change to Application.Features can't break Domain.Common.Errors.
- Position
- Below the diagonal: Application.Features uses a module listed above it, which is the healthy direction.
19→15 Application.Features uses Application.Abstractions✕
- Connections
- 3 pairs of types, where a type in Application.Features uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.DataTransferObjectResponse→Shopway.Application.Abstractions.IResponseShopway.Application.Features.DictionaryResponseEntry→Shopway.Application.Abstractions.IResponseShopway.Application.Features.PageResponse→Shopway.Application.Abstractions.IPageResponse
- Direction
- Application.Features uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features, while a change to Application.Features can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features uses a module listed above it, which is the healthy direction.
20→2 Application.Features.Products.Queries uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.ProductResponse→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursor
- Direction
- Application.Features.Products.Queries uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Application.Features.Products.Queries, while a change to Application.Features.Products.Queries can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries uses a module listed above it, which is the healthy direction.
20→15 Application.Features.Products.Queries uses Application.Abstractions✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.ProductResponse→Shopway.Application.Abstractions.IResponseShopway.Application.Features.Products.Queries.ReviewResponse→Shopway.Application.Abstractions.IResponse
- Direction
- Application.Features.Products.Queries uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries, while a change to Application.Features.Products.Queries can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries uses a module listed above it, which is the healthy direction.
21→15 Persistence.Framework uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Persistence.Framework uses a type in Application.Abstractions.
- The types involved
Shopway.Persistence.Framework.UnitOfWork→Shopway.Application.Abstractions.IUserContextService
- Direction
- Persistence.Framework uses Application.Abstractions, so a change to Application.Abstractions can break Persistence.Framework, while a change to Persistence.Framework can't break Application.Abstractions.
- Position
- Below the diagonal: Persistence.Framework uses a module listed above it, which is the healthy direction.
22→2 Application.Features.Orders.Queries uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderResponse→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursorShopway.Application.Features.Orders.Queries.PaymentResponse→Shopway.Domain.Common.DataProcessing.Abstractions.IHasCursor
- Direction
- Application.Features.Orders.Queries uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Application.Features.Orders.Queries uses a module listed above it, which is the healthy direction.
22→3 Application.Features.Orders.Queries uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Orders.Queries uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Orders.Queries uses a module listed above it, which is the healthy direction.
22→15 Application.Features.Orders.Queries uses Application.Abstractions✕
- Connections
- 4 pairs of types, where a type in Application.Features.Orders.Queries uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderResponse→Shopway.Application.Abstractions.IResponseShopway.Application.Features.Orders.Queries.OrderLineResponse→Shopway.Application.Abstractions.IResponseShopway.Application.Features.Orders.Queries.PaymentResponse→Shopway.Application.Abstractions.IResponseShopway.Application.Features.Orders.Queries.ProductSummaryResponse→Shopway.Application.Abstractions.IResponse
- Direction
- Application.Features.Orders.Queries uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Orders.Queries uses a module listed above it, which is the healthy direction.
22→16 Application.Features.Orders.Queries uses Domain.Orders✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQueryHandler→Shopway.Domain.Orders.IOrderHeaderRepository
- Direction
- Application.Features.Orders.Queries uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Orders.Queries uses a module listed above it, which is the healthy direction.
22→19 Application.Features.Orders.Queries uses Application.Features✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponse
- Direction
- Application.Features.Orders.Queries uses Application.Features, so a change to Application.Features can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Orders.Queries uses a module listed above it, which is the healthy direction.
22→30 Application.Features.Orders.Queries uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQuery→Shopway.Application.Abstractions.CQRS.IQueryShopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.IQueryHandler
- Direction
- Application.Features.Orders.Queries uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Orders.Queries, while a change to Application.Features.Orders.Queries can't break Application.Abstractions.CQRS.
- 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.
23→3 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
23→6 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQuery→Shopway.Domain.Common.DataProcessing.CursorPage
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
23→15 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryValidator→Shopway.Application.Abstractions.CursorPageQueryValidator
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
23→16 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Orders✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryHandler→Shopway.Domain.Orders.IOrderHeaderRepository
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
23→19 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Features.CursorPageResponseShopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponse
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Features, so a change to Application.Features can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
23→30 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQuery→Shopway.Application.Abstractions.CQRS.ICursorPageQueryShopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.ICursorPageQueryHandler
- Direction
- Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can't break Application.Abstractions.CQRS.
- 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.
24→3 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
24→6 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
24→15 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
24→16 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Orders✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryHandler→Shopway.Domain.Orders.IOrderHeaderRepository
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
24→19 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Features, so a change to Application.Features can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a module listed above it, which is the healthy direction.
24→30 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, while a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can't break Application.Abstractions.CQRS.
- 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.
25→3 Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.BatchUpsertProduct uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Commands.BatchUpsertProduct, while a change to Application.Features.Products.Commands.BatchUpsertProduct can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Commands.BatchUpsertProduct uses a module listed above it, which is the healthy direction.
25→4 Application.Features.Products.Commands.BatchUpsertProduct uses Domain.EntityKeys✕
- Connections
- 5 pairs of types, where a type in Application.Features.Products.Commands.BatchUpsertProduct uses a type in Domain.EntityKeys.
- The types involved
Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandHandler→Shopway.Domain.EntityKeys.ProductKeyShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandUtilities→Shopway.Domain.EntityKeys.ProductKeyShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandValidator→Shopway.Domain.EntityKeys.ProductKeyShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductResponse→Shopway.Domain.EntityKeys.ProductKeyShopway.Application.Features.Products.Commands.BatchUpsertProduct.ProductBatchUpsertRequest→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Application.Features.Products.Commands.BatchUpsertProduct uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Application.Features.Products.Commands.BatchUpsertProduct, while a change to Application.Features.Products.Commands.BatchUpsertProduct can't break Domain.EntityKeys.
- Position
- Below the diagonal: Application.Features.Products.Commands.BatchUpsertProduct uses a module listed above it, which is the healthy direction.
25→13 Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Products✕
- Connections
- 4 pairs of types, where a type in Application.Features.Products.Commands.BatchUpsertProduct uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandHandler→Shopway.Domain.Products.IProductRepositoryShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandHandler→Shopway.Domain.Products.ProductShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandUtilities→Shopway.Domain.Products.ProductShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandValidator→Shopway.Domain.Products.Product
- Direction
- Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Commands.BatchUpsertProduct, while a change to Application.Features.Products.Commands.BatchUpsertProduct can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Commands.BatchUpsertProduct uses a module listed above it, which is the healthy direction.
25→16 Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Orders✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Commands.BatchUpsertProduct uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertOrderLineCommandUtilities→Shopway.Domain.Orders.OrderLineShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertOrderLineCommandUtilities→Shopway.Domain.Orders.OrderLineKey
- Direction
- Application.Features.Products.Commands.BatchUpsertProduct uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Products.Commands.BatchUpsertProduct, while a change to Application.Features.Products.Commands.BatchUpsertProduct can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Products.Commands.BatchUpsertProduct uses a module listed above it, which is the healthy direction.
25→19 Application.Features.Products.Commands.BatchUpsertProduct uses Application.Features✕
- Connections
- 4 pairs of types, where a type in Application.Features.Products.Commands.BatchUpsertProduct uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertOrderLineCommandUtilities→Shopway.Application.Features.BatchEntryStatusShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandUtilities→Shopway.Application.Features.BatchEntryStatusShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandValidator→Shopway.Application.Features.BatchResponseEntryShopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductResponse→Shopway.Application.Features.BatchResponseEntry
- Direction
- Application.Features.Products.Commands.BatchUpsertProduct uses Application.Features, so a change to Application.Features can break Application.Features.Products.Commands.BatchUpsertProduct, while a change to Application.Features.Products.Commands.BatchUpsertProduct can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Commands.BatchUpsertProduct uses a module listed above it, which is the healthy direction.
26→3 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→6 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→13 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→15 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→17 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→18 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→19 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a module listed above it, which is the healthy direction.
26→30 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can't break Application.Abstractions.CQRS.
- 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.
27→3 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→6 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQuery→Shopway.Domain.Common.DataProcessing.CursorPage
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→13 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→15 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryValidator→Shopway.Application.Abstractions.CursorPageQueryValidator
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→17 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→18 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→19 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Features.CursorPageResponseShopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponse
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a module listed above it, which is the healthy direction.
27→30 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQuery→Shopway.Application.Abstractions.CQRS.ICursorPageQueryShopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.ICursorPageQueryHandler
- Direction
- Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, while a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can't break Application.Abstractions.CQRS.
- 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.
28→1 Persistence.Repositories uses Domain.Common.BaseTypes.Abstractions✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Domain.Common.BaseTypes.Abstractions.
- The types involved
Shopway.Persistence.Repositories.OutboxRepository→Shopway.Domain.Common.BaseTypes.Abstractions.IDomainEvent
- Direction
- Persistence.Repositories uses Domain.Common.BaseTypes.Abstractions, so a change to Domain.Common.BaseTypes.Abstractions can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Common.BaseTypes.Abstractions.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→2 Persistence.Repositories uses Domain.Common.DataProcessing.Abstractions✕
- Connections
- 8 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Common.DataProcessing.Abstractions.
- The types involved
Shopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ICursorPageShopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IFilterShopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMappingShopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IOffsetPageShopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.ISortByShopway.Persistence.Repositories.ProxyWithKeyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IIncludeBuilderShopway.Persistence.Repositories.ProxyWithKeyRepository→Shopway.Domain.Common.DataProcessing.Abstractions.IMapping
- Direction
- Persistence.Repositories uses Domain.Common.DataProcessing.Abstractions, so a change to Domain.Common.DataProcessing.Abstractions can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Common.DataProcessing.Abstractions.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→4 Persistence.Repositories uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Domain.EntityKeys.
- The types involved
Shopway.Persistence.Repositories.ProductRepository→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Persistence.Repositories uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.EntityKeys.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→6 Persistence.Repositories uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.LikeEntry
- Direction
- Persistence.Repositories uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→8 Persistence.Repositories uses Domain.Common.DataProcessing.Proxy✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Common.DataProcessing.Proxy.
- The types involved
Shopway.Persistence.Repositories.ProxyRepository→Shopway.Domain.Common.DataProcessing.Proxy.IProxyRepositoryShopway.Persistence.Repositories.ProxyWithKeyRepository→Shopway.Domain.Common.DataProcessing.Proxy.IProxyWithKeyRepository
- Direction
- Persistence.Repositories uses Domain.Common.DataProcessing.Proxy, so a change to Domain.Common.DataProcessing.Proxy can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Common.DataProcessing.Proxy.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→9 Persistence.Repositories uses Domain.Products.ValueObjects✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Domain.Products.ValueObjects.
- The types involved
Shopway.Persistence.Repositories.ProductRepository→Shopway.Domain.Products.ValueObjects.Title
- Direction
- Persistence.Repositories uses Domain.Products.ValueObjects, so a change to Domain.Products.ValueObjects can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Products.ValueObjects.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→10 Persistence.Repositories uses Domain.Users.Authorization✕
- Connections
- 3 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Users.Authorization.
- The types involved
Shopway.Persistence.Repositories.AuthorizationRepository→Shopway.Domain.Users.Authorization.IAuthorizationRepositoryShopway.Persistence.Repositories.AuthorizationRepository→Shopway.Domain.Users.Authorization.PermissionShopway.Persistence.Repositories.AuthorizationRepository→Shopway.Domain.Users.Authorization.Role
- Direction
- Persistence.Repositories uses Domain.Users.Authorization, so a change to Domain.Users.Authorization can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Users.Authorization.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→11 Persistence.Repositories uses Domain.Users.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Users.ValueObjects.
- The types involved
Shopway.Persistence.Repositories.UserRepository→Shopway.Domain.Users.ValueObjects.EmailShopway.Persistence.Repositories.UserRepository→Shopway.Domain.Users.ValueObjects.Username
- Direction
- Persistence.Repositories uses Domain.Users.ValueObjects, so a change to Domain.Users.ValueObjects can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Users.ValueObjects.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→13 Persistence.Repositories uses Domain.Products✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Products.
- The types involved
Shopway.Persistence.Repositories.ProductRepository→Shopway.Domain.Products.IProductRepositoryShopway.Persistence.Repositories.ProductRepository→Shopway.Domain.Products.Product
- Direction
- Persistence.Repositories uses Domain.Products, so a change to Domain.Products can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Products.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→14 Persistence.Repositories uses Domain.Users✕
- Connections
- 5 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Users.
- The types involved
Shopway.Persistence.Repositories.AuthorizationRepository→Shopway.Domain.Users.UserIdShopway.Persistence.Repositories.OrderHeaderRepository→Shopway.Domain.Users.UserIdShopway.Persistence.Repositories.UserRepository→Shopway.Domain.Users.IUserRepositoryShopway.Persistence.Repositories.UserRepository→Shopway.Domain.Users.UserShopway.Persistence.Repositories.UserRepository→Shopway.Domain.Users.UserId
- Direction
- Persistence.Repositories uses Domain.Users, so a change to Domain.Users can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Users.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→16 Persistence.Repositories uses Domain.Orders✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Orders.
- The types involved
Shopway.Persistence.Repositories.OrderHeaderRepository→Shopway.Domain.Orders.IOrderHeaderRepositoryShopway.Persistence.Repositories.OrderHeaderRepository→Shopway.Domain.Orders.OrderHeader
- Direction
- Persistence.Repositories uses Domain.Orders, so a change to Domain.Orders can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Orders.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
28→21 Persistence.Repositories uses Persistence.Framework✕
- Connections
- 7 pairs of types, where a type in Persistence.Repositories uses a type in Persistence.Framework.
- The types involved
Shopway.Persistence.Repositories.AuthorizationRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.OrderHeaderRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.OutboxRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.ProductRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.ProxyRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.ProxyWithKeyRepository→Shopway.Persistence.Framework.ShopwayDbContextShopway.Persistence.Repositories.UserRepository→Shopway.Persistence.Framework.ShopwayDbContext
- Direction
- Persistence.Repositories uses Persistence.Framework, so a change to Persistence.Framework can break Persistence.Repositories, while a change to Persistence.Repositories can't break Persistence.Framework.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
29→3 Application.Features.Proxy uses Domain.Common.Results✕
- Connections
- 2 pairs of types, where a type in Application.Features.Proxy uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Proxy.GenericOffsetPageQueryHandler→Shopway.Domain.Common.Results.IResultShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.Common.Results.Result
- Direction
- Application.Features.Proxy uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→4 Application.Features.Proxy uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Domain.EntityKeys.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Application.Features.Proxy uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.EntityKeys.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→6 Application.Features.Proxy uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Proxy.GenericOffsetPageQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Proxy uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→8 Application.Features.Proxy uses Domain.Common.DataProcessing.Proxy✕
- Connections
- 8 pairs of types, where a type in Application.Features.Proxy uses a type in Domain.Common.DataProcessing.Proxy.
- The types involved
Shopway.Application.Features.Proxy.GenericOffsetPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicFilterShopway.Application.Features.Proxy.GenericOffsetPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicMappingShopway.Application.Features.Proxy.GenericOffsetPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicSortByShopway.Application.Features.Proxy.GenericOffsetPageQueryHandler→Shopway.Domain.Common.DataProcessing.Proxy.IProxyRepositoryShopway.Application.Features.Proxy.GenericProxyPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicFilterShopway.Application.Features.Proxy.GenericProxyPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicMappingShopway.Application.Features.Proxy.GenericProxyPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.DynamicSortByShopway.Application.Features.Proxy.GenericProxyPageQuery→Shopway.Domain.Common.DataProcessing.Proxy.OffsetOrCursorPage
- Direction
- Application.Features.Proxy uses Domain.Common.DataProcessing.Proxy, so a change to Domain.Common.DataProcessing.Proxy can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Common.DataProcessing.Proxy.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→13 Application.Features.Proxy uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.Products.Product
- Direction
- Application.Features.Proxy uses Domain.Products, so a change to Domain.Products can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→14 Application.Features.Proxy uses Domain.Users✕
- Connections
- 2 pairs of types, where a type in Application.Features.Proxy uses a type in Domain.Users.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.Users.UserShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.Users.UserId
- Direction
- Application.Features.Proxy uses Domain.Users, so a change to Domain.Users can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Users.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→16 Application.Features.Proxy uses Domain.Orders✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Domain.Orders.OrderHeader
- Direction
- Application.Features.Proxy uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→19 Application.Features.Proxy uses Application.Features✕
- Connections
- 4 pairs of types, where a type in Application.Features.Proxy uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Proxy.GenericOffsetPageQueryHandler→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Features.Proxy.GenericOffsetPageQueryHandler→Shopway.Application.Features.OffsetPageResponseShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.PageResponse
- Direction
- Application.Features.Proxy uses Application.Features, so a change to Application.Features can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→22 Application.Features.Proxy uses Application.Features.Orders.Queries✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Application.Features.Orders.Queries.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.Orders.Queries.OrderHeaderWithMappingQuery
- Direction
- Application.Features.Proxy uses Application.Features.Orders.Queries, so a change to Application.Features.Orders.Queries can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.Orders.Queries.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→23 Application.Features.Proxy uses Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.OrderHeaderCursorPageDynamicWithMappingQuery
- Direction
- Application.Features.Proxy uses Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery, so a change to Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→24 Application.Features.Proxy uses Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.OrderHeaderOffsetPageDynamicWithMappingQuery
- Direction
- Application.Features.Proxy uses Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery, so a change to Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→26 Application.Features.Proxy uses Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery
- Direction
- Application.Features.Proxy uses Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, so a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→27 Application.Features.Proxy uses Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery✕
- Connections
- 1 pair of types, where a type in Application.Features.Proxy uses a type in Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.
- The types involved
Shopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.ProductCursorPageDynamicWithMappingQuery
- Direction
- Application.Features.Proxy uses Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery, so a change to Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery.
- Position
- Below the diagonal: Application.Features.Proxy uses a module listed above it, which is the healthy direction.
29→30 Application.Features.Proxy uses Application.Abstractions.CQRS part of a loop✕
- Connections
- 4 pairs of types, where a type in Application.Features.Proxy uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Proxy.GenericOffsetPageQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Proxy.GenericOffsetPageQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandlerShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Abstractions.CQRS.IMediatorProxyServiceShopway.Application.Features.Proxy.MediatorProxyService→Shopway.Application.Abstractions.CQRS.IQuery
- Direction
- Application.Features.Proxy uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Proxy, while a change to Application.Features.Proxy can't break Application.Abstractions.CQRS.
- 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.
30→3 Application.Abstractions.CQRS uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.CQRS uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Abstractions.CQRS.IMediatorProxyService→Shopway.Domain.Common.Results.Result
- Direction
- Application.Abstractions.CQRS uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Abstractions.CQRS, while a change to Application.Abstractions.CQRS can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Abstractions.CQRS uses a module listed above it, which is the healthy direction.
30→19 Application.Abstractions.CQRS uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Abstractions.CQRS uses a type in Application.Features.
- The types involved
Shopway.Application.Abstractions.CQRS.IMediatorProxyService→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Abstractions.CQRS.IMediatorProxyService→Shopway.Application.Features.PageResponse
- Direction
- Application.Abstractions.CQRS uses Application.Features, so a change to Application.Features can break Application.Abstractions.CQRS, while a change to Application.Abstractions.CQRS can't break Application.Features.
- Position
- Below the diagonal: Application.Abstractions.CQRS uses a module listed above it, which is the healthy direction.
30→29 Application.Abstractions.CQRS uses Application.Features.Proxy✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.CQRS uses a type in Application.Features.Proxy.
- The types involved
Shopway.Application.Abstractions.CQRS.IMediatorProxyService→Shopway.Application.Features.Proxy.GenericProxyPageQuery
- Direction
- Application.Abstractions.CQRS uses Application.Features.Proxy, so a change to Application.Features.Proxy can break Application.Abstractions.CQRS, while a change to Application.Abstractions.CQRS can't break Application.Features.Proxy.
- Position
- Below the diagonal: Application.Abstractions.CQRS uses a module listed above it, which is the healthy direction.
31→3 Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Common.Results✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandHandler→Shopway.Domain.Common.Results.IResultShopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderOpenTelemetryPipeline→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
31→12 Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Orders.ValueObjects✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Domain.Orders.ValueObjects.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandHandler→Shopway.Domain.Orders.ValueObjects.Discount
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Orders.ValueObjects, so a change to Domain.Orders.ValueObjects can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Domain.Orders.ValueObjects.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
31→14 Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Users✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Domain.Users.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommand→Shopway.Domain.Users.UserId
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Users, so a change to Domain.Users can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Domain.Users.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
31→15 Application.Features.Orders.Commands.CreateHeaderOrder uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderResponse→Shopway.Application.Abstractions.IResponse
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
31→16 Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Orders✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandHandler→Shopway.Domain.Orders.IOrderHeaderRepositoryShopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandHandler→Shopway.Domain.Orders.OrderHeader
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
31→30 Application.Features.Orders.Commands.CreateHeaderOrder uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Orders.Commands.CreateHeaderOrder uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommand→Shopway.Application.Abstractions.CQRS.ICommandShopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandHandler→Shopway.Application.Abstractions.CQRS.ICommandHandler
- Direction
- Application.Features.Orders.Commands.CreateHeaderOrder uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Orders.Commands.CreateHeaderOrder, while a change to Application.Features.Orders.Commands.CreateHeaderOrder can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Orders.Commands.CreateHeaderOrder uses a module listed above it, which is the healthy direction.
32→3 Application.Features.Products.Commands.AddReview uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Commands.AddReview uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
32→9 Application.Features.Products.Commands.AddReview uses Domain.Products.ValueObjects✕
- Connections
- 3 pairs of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Domain.Products.ValueObjects.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Products.ValueObjects.DescriptionShopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Products.ValueObjects.StarsShopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Products.ValueObjects.Title
- Direction
- Application.Features.Products.Commands.AddReview uses Domain.Products.ValueObjects, so a change to Domain.Products.ValueObjects can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Domain.Products.ValueObjects.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
32→11 Application.Features.Products.Commands.AddReview uses Domain.Users.ValueObjects✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Domain.Users.ValueObjects.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Users.ValueObjects.Username
- Direction
- Application.Features.Products.Commands.AddReview uses Domain.Users.ValueObjects, so a change to Domain.Users.ValueObjects can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Domain.Users.ValueObjects.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
32→13 Application.Features.Products.Commands.AddReview uses Domain.Products✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Products.IProductRepositoryShopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Domain.Products.Review
- Direction
- Application.Features.Products.Commands.AddReview uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
32→15 Application.Features.Products.Commands.AddReview uses Application.Abstractions✕
- Connections
- 3 pairs of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Application.Abstractions.IUserContextServiceShopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Application.Abstractions.IValidatorShopway.Application.Features.Products.Commands.AddReview.AddReviewResponse→Shopway.Application.Abstractions.IResponse
- Direction
- Application.Features.Products.Commands.AddReview uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
32→30 Application.Features.Products.Commands.AddReview uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Commands.AddReview uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Commands.AddReview.AddReviewCommand→Shopway.Application.Abstractions.CQRS.ICommandShopway.Application.Features.Products.Commands.AddReview.AddReviewCommandHandler→Shopway.Application.Abstractions.CQRS.ICommandHandler
- Direction
- Application.Features.Products.Commands.AddReview uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Commands.AddReview, while a change to Application.Features.Products.Commands.AddReview can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Commands.AddReview uses a module listed above it, which is the healthy direction.
33→3 Application.Features.Products.Commands.RemoveReview uses Domain.Common.Results✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Commands.RemoveReview uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Commands.RemoveReview.RemoveOrderLineCommandHandler→Shopway.Domain.Common.Results.IResultShopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewCommandHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Commands.RemoveReview uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Commands.RemoveReview, while a change to Application.Features.Products.Commands.RemoveReview can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Commands.RemoveReview uses a module listed above it, which is the healthy direction.
33→13 Application.Features.Products.Commands.RemoveReview uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.RemoveReview uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewCommandHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Commands.RemoveReview uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Commands.RemoveReview, while a change to Application.Features.Products.Commands.RemoveReview can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Commands.RemoveReview uses a module listed above it, which is the healthy direction.
33→15 Application.Features.Products.Commands.RemoveReview uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.RemoveReview uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewResponse→Shopway.Application.Abstractions.IResponse
- Direction
- Application.Features.Products.Commands.RemoveReview uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Commands.RemoveReview, while a change to Application.Features.Products.Commands.RemoveReview can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Commands.RemoveReview uses a module listed above it, which is the healthy direction.
33→16 Application.Features.Products.Commands.RemoveReview uses Domain.Orders✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.RemoveReview uses a type in Domain.Orders.
- The types involved
Shopway.Application.Features.Products.Commands.RemoveReview.RemoveOrderLineCommandHandler→Shopway.Domain.Orders.IOrderHeaderRepository
- Direction
- Application.Features.Products.Commands.RemoveReview uses Domain.Orders, so a change to Domain.Orders can break Application.Features.Products.Commands.RemoveReview, while a change to Application.Features.Products.Commands.RemoveReview can't break Domain.Orders.
- Position
- Below the diagonal: Application.Features.Products.Commands.RemoveReview uses a module listed above it, which is the healthy direction.
33→30 Application.Features.Products.Commands.RemoveReview uses Application.Abstractions.CQRS✕
- Connections
- 3 pairs of types, where a type in Application.Features.Products.Commands.RemoveReview uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Commands.RemoveReview.RemoveOrderLineCommandHandler→Shopway.Application.Abstractions.CQRS.ICommandHandlerShopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewCommand→Shopway.Application.Abstractions.CQRS.ICommandShopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewCommandHandler→Shopway.Application.Abstractions.CQRS.ICommandHandler
- Direction
- Application.Features.Products.Commands.RemoveReview uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Commands.RemoveReview, while a change to Application.Features.Products.Commands.RemoveReview can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Commands.RemoveReview uses a module listed above it, which is the healthy direction.
34→3 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→6 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→13 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→15 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→17 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductDynamicFilter
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→18 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→19 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Features✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→20 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Features.Products.Queries✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Application.Features.Products.Queries.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryHandler→Shopway.Application.Features.Products.Queries.ProductResponse
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Features.Products.Queries, so a change to Application.Features.Products.Queries can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Application.Features.Products.Queries.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
34→30 Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.DynamicOffsetProductQuery uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Products.Queries.DynamicOffsetProductQuery uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.DynamicOffsetProductQuery, while a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Queries.DynamicOffsetProductQuery uses a module listed above it, which is the healthy direction.
35→3 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→4 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.EntityKeys.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.EntityKeys.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→6 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQuery→Shopway.Domain.Common.DataProcessing.CursorPage
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→13 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→15 Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryValidator→Shopway.Application.Abstractions.CursorPageQueryValidator
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→17 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductDictionaryStaticFilter
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→18 Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→19 Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Application.Features.CursorPageResponseShopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Application.Features.DictionaryResponseEntry
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
35→30 Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.GetProductsCursorDictionary uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQuery→Shopway.Application.Abstractions.CQRS.ICursorPageQueryShopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQueryHandler→Shopway.Application.Abstractions.CQRS.ICursorPageQueryHandler
- Direction
- Application.Features.Products.Queries.GetProductsCursorDictionary uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.GetProductsCursorDictionary, while a change to Application.Features.Products.Queries.GetProductsCursorDictionary can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsCursorDictionary uses a module listed above it, which is the healthy direction.
36→3 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→4 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.EntityKeys.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.EntityKeys.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→6 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→13 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→15 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→17 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductDictionaryStaticFilter
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→18 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductDynamicSortBy
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→19 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Application.Features.DictionaryResponseEntryShopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
36→30 Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.GetProductsOffsetDictionary uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Products.Queries.GetProductsOffsetDictionary uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.GetProductsOffsetDictionary, while a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetProductsOffsetDictionary uses a module listed above it, which is the healthy direction.
37→3 Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→6 Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→13 Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→15 Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→17 Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductStaticFilter
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→18 Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductStaticSortBy
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→19 Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Features✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→20 Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Features.Products.Queries✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Application.Features.Products.Queries.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryHandler→Shopway.Application.Features.Products.Queries.ProductResponse
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Features.Products.Queries, so a change to Application.Features.Products.Queries can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Application.Features.Products.Queries.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
37→30 Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProduct uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProduct uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.QueryOffsetPageProduct, while a change to Application.Features.Products.Queries.QueryOffsetPageProduct can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProduct uses a module listed above it, which is the healthy direction.
38→3 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Common.Results✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Domain.Common.Results.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryHandler→Shopway.Domain.Common.Results.IResult
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Common.Results, so a change to Domain.Common.Results can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Domain.Common.Results.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→6 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQuery→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→13 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Domain.Products.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryHandler→Shopway.Domain.Products.IProductRepository
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products, so a change to Domain.Products can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Domain.Products.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→15 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Application.Abstractions.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryValidator→Shopway.Application.Abstractions.OffsetPageQueryValidator
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Abstractions, so a change to Application.Abstractions can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Application.Abstractions.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→17 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products.DataProcessing.Filtering✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Domain.Products.DataProcessing.Filtering.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQuery→Shopway.Domain.Products.DataProcessing.Filtering.ProductStaticFilter
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products.DataProcessing.Filtering, so a change to Domain.Products.DataProcessing.Filtering can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Domain.Products.DataProcessing.Filtering.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→18 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products.DataProcessing.Sorting✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Domain.Products.DataProcessing.Sorting.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQuery→Shopway.Domain.Products.DataProcessing.Sorting.ProductStaticSortBy
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Domain.Products.DataProcessing.Sorting, so a change to Domain.Products.DataProcessing.Sorting can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Domain.Products.DataProcessing.Sorting.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→19 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Features✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Application.Features.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryHandler→Shopway.Application.Features.DataTransferObjectResponseShopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryHandler→Shopway.Application.Features.OffsetPageResponse
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Features, so a change to Application.Features can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Application.Features.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
38→30 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Abstractions.CQRS✕
- Connections
- 2 pairs of types, where a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQuery→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryShopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQueryHandler→Shopway.Application.Abstractions.CQRS.IOffsetPageQueryHandler
- Direction
- Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, while a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Application.Features.Products.Queries.QueryOffsetPageProductWithMapping uses a module listed above it, which is the healthy direction.
39→4 Application.Mappings uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Application.Mappings uses a type in Domain.EntityKeys.
- The types involved
Shopway.Application.Mappings.ProductMapping→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Application.Mappings uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Application.Mappings, while a change to Application.Mappings can't break Domain.EntityKeys.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→10 Application.Mappings uses Domain.Users.Authorization✕
- Connections
- 2 pairs of types, where a type in Application.Mappings uses a type in Domain.Users.Authorization.
- The types involved
Shopway.Application.Mappings.PermissionMapping→Shopway.Domain.Users.Authorization.PermissionShopway.Application.Mappings.UserMapping→Shopway.Domain.Users.Authorization.Role
- Direction
- Application.Mappings uses Domain.Users.Authorization, so a change to Domain.Users.Authorization can break Application.Mappings, while a change to Application.Mappings can't break Domain.Users.Authorization.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→12 Application.Mappings uses Domain.Orders.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Application.Mappings uses a type in Domain.Orders.ValueObjects.
- The types involved
Shopway.Application.Mappings.PaymentMapping→Shopway.Domain.Orders.ValueObjects.SessionShopway.Application.Mappings.ProductMapping→Shopway.Domain.Orders.ValueObjects.ProductSummary
- Direction
- Application.Mappings uses Domain.Orders.ValueObjects, so a change to Domain.Orders.ValueObjects can break Application.Mappings, while a change to Application.Mappings can't break Domain.Orders.ValueObjects.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→13 Application.Mappings uses Domain.Products✕
- Connections
- 2 pairs of types, where a type in Application.Mappings uses a type in Domain.Products.
- The types involved
Shopway.Application.Mappings.ProductMapping→Shopway.Domain.Products.ProductShopway.Application.Mappings.ReviewMapping→Shopway.Domain.Products.Review
- Direction
- Application.Mappings uses Domain.Products, so a change to Domain.Products can break Application.Mappings, while a change to Application.Mappings can't break Domain.Products.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→14 Application.Mappings uses Domain.Users✕
- Connections
- 1 pair of types, where a type in Application.Mappings uses a type in Domain.Users.
- The types involved
Shopway.Application.Mappings.UserMapping→Shopway.Domain.Users.User
- Direction
- Application.Mappings uses Domain.Users, so a change to Domain.Users can break Application.Mappings, while a change to Application.Mappings can't break Domain.Users.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→16 Application.Mappings uses Domain.Orders✕
- Connections
- 4 pairs of types, where a type in Application.Mappings uses a type in Domain.Orders.
- The types involved
Shopway.Application.Mappings.OrderHeaderMapping→Shopway.Domain.Orders.OrderHeaderShopway.Application.Mappings.OrderLineMapping→Shopway.Domain.Orders.OrderLineShopway.Application.Mappings.OrderLineMapping→Shopway.Domain.Orders.OrderLineKeyShopway.Application.Mappings.PaymentMapping→Shopway.Domain.Orders.Payment
- Direction
- Application.Mappings uses Domain.Orders, so a change to Domain.Orders can break Application.Mappings, while a change to Application.Mappings can't break Domain.Orders.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→19 Application.Mappings uses Application.Features✕
- Connections
- 3 pairs of types, where a type in Application.Mappings uses a type in Application.Features.
- The types involved
Shopway.Application.Mappings.OrderLineMapping→Shopway.Application.Features.BatchResponseEntryShopway.Application.Mappings.ProductMapping→Shopway.Application.Features.BatchResponseEntryShopway.Application.Mappings.ProductMapping→Shopway.Application.Features.DictionaryResponseEntry
- Direction
- Application.Mappings uses Application.Features, so a change to Application.Features can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→20 Application.Mappings uses Application.Features.Products.Queries✕
- Connections
- 2 pairs of types, where a type in Application.Mappings uses a type in Application.Features.Products.Queries.
- The types involved
Shopway.Application.Mappings.ProductMapping→Shopway.Application.Features.Products.Queries.ProductResponseShopway.Application.Mappings.ReviewMapping→Shopway.Application.Features.Products.Queries.ReviewResponse
- Direction
- Application.Mappings uses Application.Features.Products.Queries, so a change to Application.Features.Products.Queries can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Products.Queries.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→22 Application.Mappings uses Application.Features.Orders.Queries✕
- Connections
- 4 pairs of types, where a type in Application.Mappings uses a type in Application.Features.Orders.Queries.
- The types involved
Shopway.Application.Mappings.OrderHeaderMapping→Shopway.Application.Features.Orders.Queries.OrderHeaderResponseShopway.Application.Mappings.OrderLineMapping→Shopway.Application.Features.Orders.Queries.OrderLineResponseShopway.Application.Mappings.PaymentMapping→Shopway.Application.Features.Orders.Queries.PaymentResponseShopway.Application.Mappings.ProductMapping→Shopway.Application.Features.Orders.Queries.ProductSummaryResponse
- Direction
- Application.Mappings uses Application.Features.Orders.Queries, so a change to Application.Features.Orders.Queries can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Orders.Queries.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→25 Application.Mappings uses Application.Features.Products.Commands.BatchUpsertProduct✕
- Connections
- 2 pairs of types, where a type in Application.Mappings uses a type in Application.Features.Products.Commands.BatchUpsertProduct.
- The types involved
Shopway.Application.Mappings.ProductMapping→Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductResponseShopway.Application.Mappings.ProductMapping→Shopway.Application.Features.Products.Commands.BatchUpsertProduct.ProductBatchUpsertRequest
- Direction
- Application.Mappings uses Application.Features.Products.Commands.BatchUpsertProduct, so a change to Application.Features.Products.Commands.BatchUpsertProduct can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Products.Commands.BatchUpsertProduct.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→31 Application.Mappings uses Application.Features.Orders.Commands.CreateHeaderOrder✕
- Connections
- 1 pair of types, where a type in Application.Mappings uses a type in Application.Features.Orders.Commands.CreateHeaderOrder.
- The types involved
Shopway.Application.Mappings.OrderHeaderMapping→Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderResponse
- Direction
- Application.Mappings uses Application.Features.Orders.Commands.CreateHeaderOrder, so a change to Application.Features.Orders.Commands.CreateHeaderOrder can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Orders.Commands.CreateHeaderOrder.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→32 Application.Mappings uses Application.Features.Products.Commands.AddReview✕
- Connections
- 1 pair of types, where a type in Application.Mappings uses a type in Application.Features.Products.Commands.AddReview.
- The types involved
Shopway.Application.Mappings.ReviewMapping→Shopway.Application.Features.Products.Commands.AddReview.AddReviewResponse
- Direction
- Application.Mappings uses Application.Features.Products.Commands.AddReview, so a change to Application.Features.Products.Commands.AddReview can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Products.Commands.AddReview.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
39→33 Application.Mappings uses Application.Features.Products.Commands.RemoveReview✕
- Connections
- 1 pair of types, where a type in Application.Mappings uses a type in Application.Features.Products.Commands.RemoveReview.
- The types involved
Shopway.Application.Mappings.ReviewMapping→Shopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewResponse
- Direction
- Application.Mappings uses Application.Features.Products.Commands.RemoveReview, so a change to Application.Features.Products.Commands.RemoveReview can break Application.Mappings, while a change to Application.Mappings can't break Application.Features.Products.Commands.RemoveReview.
- Position
- Below the diagonal: Application.Mappings uses a module listed above it, which is the healthy direction.
40→4 Presentation.Controllers uses Domain.EntityKeys✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Domain.EntityKeys.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Domain.EntityKeys.ProductKey
- Direction
- Presentation.Controllers uses Domain.EntityKeys, so a change to Domain.EntityKeys can break Presentation.Controllers, while a change to Presentation.Controllers can't break Domain.EntityKeys.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→6 Presentation.Controllers uses Domain.Common.DataProcessing✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Domain.Common.DataProcessing.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Domain.Common.DataProcessing.OffsetPage
- Direction
- Presentation.Controllers uses Domain.Common.DataProcessing, so a change to Domain.Common.DataProcessing can break Presentation.Controllers, while a change to Presentation.Controllers can't break Domain.Common.DataProcessing.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→19 Presentation.Controllers uses Application.Features✕
- Connections
- 5 pairs of types, where a type in Presentation.Controllers uses a type in Application.Features.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.CursorPageResponseShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.DataTransferObjectResponseShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.DictionaryResponseEntryShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.OffsetPageResponseShopway.Presentation.Controllers.ProxyController→Shopway.Application.Features.DataTransferObjectResponse
- Direction
- Presentation.Controllers uses Application.Features, so a change to Application.Features can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→20 Presentation.Controllers uses Application.Features.Products.Queries✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.ProductResponse
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries, so a change to Application.Features.Products.Queries can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→22 Presentation.Controllers uses Application.Features.Orders.Queries✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Orders.Queries.
- The types involved
Shopway.Presentation.Controllers.OrderHeadersController→Shopway.Application.Features.Orders.Queries.OrderHeaderResponse
- Direction
- Presentation.Controllers uses Application.Features.Orders.Queries, so a change to Application.Features.Orders.Queries can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Orders.Queries.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→25 Presentation.Controllers uses Application.Features.Products.Commands.BatchUpsertProduct✕
- Connections
- 2 pairs of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Commands.BatchUpsertProduct.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductCommandShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.BatchUpsertProduct.BatchUpsertProductResponse
- Direction
- Presentation.Controllers uses Application.Features.Products.Commands.BatchUpsertProduct, so a change to Application.Features.Products.Commands.BatchUpsertProduct can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Commands.BatchUpsertProduct.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→26 Presentation.Controllers uses Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.ProductOffsetPageDynamicWithMappingQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery, so a change to Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→29 Presentation.Controllers uses Application.Features.Proxy✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Proxy.
- The types involved
Shopway.Presentation.Controllers.ProxyController→Shopway.Application.Features.Proxy.GenericProxyPageQuery
- Direction
- Presentation.Controllers uses Application.Features.Proxy, so a change to Application.Features.Proxy can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Proxy.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→30 Presentation.Controllers uses Application.Abstractions.CQRS✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Abstractions.CQRS.
- The types involved
Shopway.Presentation.Controllers.ProxyController→Shopway.Application.Abstractions.CQRS.IMediatorProxyService
- Direction
- Presentation.Controllers uses Application.Abstractions.CQRS, so a change to Application.Abstractions.CQRS can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Abstractions.CQRS.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→31 Presentation.Controllers uses Application.Features.Orders.Commands.CreateHeaderOrder✕
- Connections
- 2 pairs of types, where a type in Presentation.Controllers uses a type in Application.Features.Orders.Commands.CreateHeaderOrder.
- The types involved
Shopway.Presentation.Controllers.OrderHeadersController→Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderCommandShopway.Presentation.Controllers.OrderHeadersController→Shopway.Application.Features.Orders.Commands.CreateHeaderOrder.CreateOrderHeaderResponse
- Direction
- Presentation.Controllers uses Application.Features.Orders.Commands.CreateHeaderOrder, so a change to Application.Features.Orders.Commands.CreateHeaderOrder can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Orders.Commands.CreateHeaderOrder.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→32 Presentation.Controllers uses Application.Features.Products.Commands.AddReview✕
- Connections
- 2 pairs of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Commands.AddReview.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.AddReview.AddReviewRequestBodyShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.AddReview.AddReviewResponse
- Direction
- Presentation.Controllers uses Application.Features.Products.Commands.AddReview, so a change to Application.Features.Products.Commands.AddReview can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Commands.AddReview.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→33 Presentation.Controllers uses Application.Features.Products.Commands.RemoveReview✕
- Connections
- 2 pairs of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Commands.RemoveReview.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewCommandShopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Commands.RemoveReview.RemoveReviewResponse
- Direction
- Presentation.Controllers uses Application.Features.Products.Commands.RemoveReview, so a change to Application.Features.Products.Commands.RemoveReview can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Commands.RemoveReview.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→34 Presentation.Controllers uses Application.Features.Products.Queries.DynamicOffsetProductQuery✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.DynamicOffsetProductQuery.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.DynamicOffsetProductQuery.ProductOffsetPageDynamicQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.DynamicOffsetProductQuery, so a change to Application.Features.Products.Queries.DynamicOffsetProductQuery can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.DynamicOffsetProductQuery.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→35 Presentation.Controllers uses Application.Features.Products.Queries.GetProductsCursorDictionary✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.GetProductsCursorDictionary.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.GetProductsCursorDictionary.ProductDictionaryCursorPageQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.GetProductsCursorDictionary, so a change to Application.Features.Products.Queries.GetProductsCursorDictionary can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.GetProductsCursorDictionary.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→36 Presentation.Controllers uses Application.Features.Products.Queries.GetProductsOffsetDictionary✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.GetProductsOffsetDictionary.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.GetProductsOffsetDictionary.ProductDictionaryOffsetPageQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.GetProductsOffsetDictionary, so a change to Application.Features.Products.Queries.GetProductsOffsetDictionary can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.GetProductsOffsetDictionary.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→37 Presentation.Controllers uses Application.Features.Products.Queries.QueryOffsetPageProduct✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.QueryOffsetPageProduct.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.QueryOffsetPageProduct.ProductOffsetPageQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.QueryOffsetPageProduct, so a change to Application.Features.Products.Queries.QueryOffsetPageProduct can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.QueryOffsetPageProduct.
- Position
- Below the diagonal: Presentation.Controllers uses a module listed above it, which is the healthy direction.
40→38 Presentation.Controllers uses Application.Features.Products.Queries.QueryOffsetPageProductWithMapping✕
- Connections
- 1 pair of types, where a type in Presentation.Controllers uses a type in Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.
- The types involved
Shopway.Presentation.Controllers.ProductsController→Shopway.Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.ProductOffsetPageWithMappingQuery
- Direction
- Presentation.Controllers uses Application.Features.Products.Queries.QueryOffsetPageProductWithMapping, so a change to Application.Features.Products.Queries.QueryOffsetPageProductWithMapping can break Presentation.Controllers, while a change to Presentation.Controllers can't break Application.Features.Products.Queries.QueryOffsetPageProductWithMapping.
- Position
- Below the diagonal: Presentation.Controllers 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A07:2025 — Authentication Failures | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 19 | High / Critical |
| A02:2025 — Security Misconfiguration | 16 | High / Critical |
Roadmap
Top priorities: Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3), REDACTED (2); Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with Shopway.Presentation.csproj (4), REDACTED, REDACTED; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with Shopway.Presentation.csproj (4), REDACTED, REDACTED. | +8.2 pts | Low | Dependency Hygiene |
| Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3), REDACTED (2). | +11.3 pts | Medium | REDACTED Scanning |
| Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, Shopway.Tests.Unit.csproj, Shopway.Tests.Integration.csproj. | +5.3 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.5 pts | Low | ADR Quality |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.9 pts | Medium | DR & Backup |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.7 pts | Medium | Security & performance tooling |
| Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. | +2.1 pts | Low | Dependency Hygiene |
| Resolve the 3 redundant comment finding(s) in Comment Value — start with REDACTED, ValueObject.cs, ShopwayApiFactory.cs. | +1.8 pts | Low | Comment Value |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.5 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.3 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs | 6.1 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
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 98 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 — 98 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, 379 of 448 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
- 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. All 110 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 110 of the 720 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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 C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
- 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.
- D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — 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. Large codebase (23,653 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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. `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, … (+156 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 15 — the compose project is invalid) — time="2026-11-08T08:37:04Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T08:37:04Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "portainer" has neither an image nor a build context specified: invalid compose project; 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.
- ED5 Idempotency — 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. Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: Syntax node is not within syntax tree.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED 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.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- 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.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- 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.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StringUtilities.SqlLike at 35.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with StringUtilities.SqlLike (cyclomatic 35). — Refactoring it lifts Cyclomatic Complexity from 9.0 to about 10.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 StringUtilities.SqlLike at 83.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with StringUtilities.SqlLike (cognitive 83), FilterByEntryJsonConverter.Read (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.8 to about 8.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Error.Common.cs. — 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
34 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), FluentValidationUtilities.cs, GenericFluentValidationUtilities.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ApplicationCache.AllowedFilterOperations.cs, AddPermissionToRoleCommandHandler.cs, HashUtilities.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with OrderLineKeyJsonConverter.cs, ProductName.cs, AccessToken.cs. — One of this dimension's main actionable groups (4 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)
2 of 55 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with Specification.cs, User.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
109 test methods: 97 unit, 12 integration, 0 BDD, 0 e2e.
D10 · Test Quality
1 skipped (1 with a documented reason), 0 zero-assertion, 3 mock references across 109 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D12 · Dependency Hygiene
53 outdated, 3 vulnerable, 2 deprecated, 2 prerelease packages.
What to do
- Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with Shopway.Presentation.csproj (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, Shopway.Tests.Unit.csproj, Shopway.Tests.Integration.csproj. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
5 secret(s) detected.
What to do
- Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 295 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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
7 deducted debt markers + unmeasured dead symbols across 23653 LoC in the .NET projects (0.2/KLoC) → score 9.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AddRoleToUserCommandHandler.cs, RemoveRoleFromUserCommandHandler.cs, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Shopway.Presentation.csproj. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with ReflectionUtilitiesBenchmarks.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
18 projects, 897 source files, 29259 hand-written lines of code (23653 production / 5606 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 20928 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 27 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 15 document(s) read across 10 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
3 of 99 judged comments only repeat the code they sit on (3.0 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with REDACTED, ValueObject.cs, ShopwayApiFactory.cs. — One of this dimension's main actionable groups (3 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 REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
91 % of calls cross a namespace and 18 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What to do
- Improve Navigability — currently 8.2/10. — 91 % of calls cross a namespace and 18 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
23 finding(s): 0 critical, 23 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 15 REDACTED finding(s) in Secrets (history) — start with REDACTED (9), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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)
41 finding(s): 0 critical, 5 high, 36 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 165 file(s) — `PaymentGateway/Webhook/WebhookService.cs` (line 8), `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs` (lines 8–11, line 12, lines 13–15), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs` (line 12, line 17, line 28), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs` (line 37, line 39), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs` (line 12, line 17, line 28), … (+160 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 155 of those file(s) — `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdGenerator/EntityIdGenerator.cs`, … (+150 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 7 of those file(s) — `src/Shopway.Application/Exceptions/BadRequestException.cs`, `src/Shopway.Application/Exceptions/ForbidException.cs`, `src/Shopway.Application/Exceptions/NotFoundException.cs`, `src/Shopway.Application/Exceptions/UnavailableException.cs`, `src/Shopway.Domain/Common/Exceptions/DomainException.cs`, … (+2 more) — 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.
What to do
- Resolve the 33 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (13), REDACTED (9), REDACTED (5). — One of this dimension's main actionable groups (33 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
19 finding(s): 3 critical, 10 high, 6 medium, 0 low.
What to do
- Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 8 high, 5 medium, 2 low.
What to do
- Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
110 of 110 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 110 of the 720 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 110 Orphaned file finding(s) in Knowledge Freshness — start with QueryableUtilities.cs (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (110 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ProductDictionaryCursorPageQueryHandler.cs↔ProductOffsetPageQueryHandler.cs 90%; ProductDictionaryCursorPageQueryHandler.cs↔ProductRepository.cs 70%; ProductOffsetPageQueryHandler.cs↔ProductRepository.cs 62%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with ProductOffsetPageQueryHandler.cs (2), ProductRepository.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with ProductDictionaryCursorPageQueryHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
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 18 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
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `WebhookService` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions; e.g. `_subscriptions` at line 14). — PaymentGateway/Webhook/WebhookService.cs:8
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
- The namespaces Shopway.Domain.Common.Errors ↔ Shopway.Domain.Common.Results ↔ Shopway.Domain.Common.Results.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.Results → Shopway.Domain.Common.Results.Abstractions (Shopway.Domain.Common.Results.ValidationResult → Shopway.Domain.Common.Results.Abstractions.IValidationResult, 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/Shopway.Domain/Common/Results/ValidationResult.cs:2
- The namespaces Shopway.Domain.Users ↔ Shopway.Domain.Users.Authorization depend on each other. The lightest dependency in the cycle is Shopway.Domain.Users → Shopway.Domain.Users.Authorization (Shopway.Domain.Users.User → Shopway.Domain.Users.Authorization.Role, 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/Shopway.Domain/Users/User.cs:3
- The namespaces Shopway.Application.Abstractions ↔ Shopway.Application.Features.Users.Commands depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions → Shopway.Application.Features.Users.Commands (Shopway.Application.Abstractions.ISecurityTokenService → Shopway.Application.Features.Users.Commands.AccessTokenResponse, 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/Shopway.Application/Abstractions/ISecurityTokenService.cs:1
- The namespaces Shopway.Persistence.Abstractions ↔ Shopway.Persistence.Framework depend on each other. The lightest dependency in the cycle is Shopway.Persistence.Framework → Shopway.Persistence.Abstractions (Shopway.Persistence.Framework.UnitOfWork → Shopway.Persistence.Abstractions.IUnitOfWork, 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/Shopway.Persistence/Framework/UnitOfWork.cs:8
- The namespaces Shopway.Domain.Common.DataProcessing ↔ Shopway.Domain.Common.DataProcessing.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.DataProcessing.Abstractions → Shopway.Domain.Common.DataProcessing (Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilter → Shopway.Domain.Common.DataProcessing.FilterByEntry, 4 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/Shopway.Domain/Common/DataProcessing/Abstractions/IDynamicFilter.cs:5
- The namespaces Shopway.Domain.EntityKeys ↔ Shopway.Domain.Products depend on each other. The lightest dependency in the cycle is Shopway.Domain.EntityKeys → Shopway.Domain.Products (Shopway.Domain.EntityKeys.ProductKey → Shopway.Domain.Products.Product, 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/Shopway.Domain/Products/ProductKey.cs:2
- The namespaces Shopway.Application.Abstractions.CQRS ↔ Shopway.Application.Features.Orders.Queries ↔ Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery ↔ Shopway.Application.Features.Proxy ↔ Shopway.Application.Features.Proxy.GenericPageQuery ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryById ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryByKey depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions.CQRS → Shopway.Application.Features.Proxy (Shopway.Application.Abstractions.CQRS.IMediatorProxyService → Shopway.Application.Features.Proxy.GenericProxyPageQuery, 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/Shopway.Application/Abstractions/CQRS/IMediatorProxyService.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
- `IProductRepository` declares 20 members under just 15 distinct name(s): `GetNamesAsync`, `GetByKeyOrDefaultAsync`, `AnyAsync`, `AnyAsync`, `VerifyIdsAsync`, `GetByIdAsync`, `GetByIdsAsync`, `GetByIdWithReviewAsync`, `GetByIdWithReviewAsync`, `GetByIdWithIncludesAsync`, `GetProductsDictionaryByNameAndRevision`, `Create`, `Update`, `Remove`, `PageAsync`, `PageAsync`, `QueryByIdAsync`, `QueryByIdAsync`, `QueryByKeyAsync`, `QueryByKeyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Shopway.Domain/Products/IProductRepository.cs:9
What to do
- Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX7 · Slice cohesion
- `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderOffsetPageDynamicWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:16
- `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderCursorPageDynamicWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:32
- `MediatorProxyService` (slice 'Proxy') depends on `ProductOffsetPageDynamicWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:16
- `MediatorProxyService` (slice 'Proxy') depends on `ProductCursorPageDynamicWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:32
- `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.OrderHeaders.cs:11
- `MediatorProxyService` (slice 'Proxy') depends on `ProductWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.Products.cs:11
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
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
- Access here is not default-deny: `UsersController.Register` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:42
- Access here is not default-deny: `UsersController.Login` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:58
- Access here is not default-deny: `UsersController.LoginTwoFactorFirstStep` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:74
- Access here is not default-deny: `UsersController.LoginTwoFactorSecondStep` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:90
- Access here is not default-deny: `UsersController.LoginTwoFactorTopt` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:119
- Access here is not default-deny: `UsersController.Refresh` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:135
- Access here is not default-deny: `UsersController.GetUserByUsername` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:171
- Access here is not default-deny: `UsersController.GetUserRolesByUsername` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:188
- Access here is not default-deny: `UsersController.GetRolesWithPermissions` declares no authorization while 12 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:205
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
C3 · Audit Trail
- An audit marker (IAuditable / AddAuditing) was found, but no structural mechanism (an EF SaveChanges interceptor, an immutable audit-log type, or [Audited] usage) — the trail's completeness can't be confirmed from the source.
What to do
- Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `CachedOrderHeaderRepository.Update` saves `IOrderHeaderRepository`, `CacheUtilities` 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/Shopway.Persistence/Repositories/Decorators/CachedOrderHeaderRepository.cs:58
- `CachedProductRepository.Update` saves `IProductRepository`, `CacheUtilities` 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/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:56
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
- `OrderHeader` reads `DateTimeOffset.UtcNow` inside `SoftDelete` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Shopway.Domain/Orders/OrderHeader.cs:130
- `User` reads `DateTimeOffset.UtcNow` inside `SetTwoFactorToken` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Shopway.Domain/Users/User.cs:66
What to do
- Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM4 · Rich vs anemic model
- `OrderLine` 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/Shopway.Domain/Orders/OrderLine.cs:7
- `Review` 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/Shopway.Domain/Products/Review.cs:8
- `Customer` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Shopway.Domain/Users/Customer.cs:8
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
- `DataTransferObject` exposes publicly writable state (this[]). — src/Shopway.Domain/Common/DataProcessing/DataTransferObject.cs:10
- `OrderHeader` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, SoftDeletedOn, SoftDeleted). — src/Shopway.Domain/Orders/OrderHeader.cs:17
- `OrderLine` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Orders/OrderLine.cs:7
- `Payment` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Orders/Payment.cs:13
- `Product` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Products/Product.cs:8
- `Review` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Products/Review.cs:8
- `Customer` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Users/Customer.cs:8
- `User` exposes publicly writable state (Username, Email, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, and 5 more). — src/Shopway.Domain/Users/User.cs:9
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
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
- `MimeKitEmailSender.SendEmailAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Shopway.Infrastructure/Services/MimeKitEmailSender.cs:15
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `GetHashCode` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Shopway.Domain/Common/Utilities/IEnumerableUtilities.cs:123
- `CreateAsync` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Refunds/RefundService.cs:5
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — src/Shopway.Application/Features/Proxy/GenericPageQuery/GenericPageQueryStrategyAttribute.cs:28, src/Shopway.Application/Features/Proxy/GenericQuery/QueryById/GenericStrategyByIdAttribute.cs:26, src/Shopway.Application/Features/Proxy/GenericQuery/QueryByKey/GenericStrategyByKeyAttribute.cs:26, …
- A test is skipped ("Only for cleaning the database manually") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 9 of 9 project(s) that lack one — worth up to 2 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
P1 · CI/CD gates
P10 · Library API & versioning
What to do
- Make types internal by default and expose only the deliberate public API — even for a small library, every public type is a stability contract.
P2 · Observability
- Only 4/6 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 6, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
- `src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs` reports through `Console.Write…` at line 13 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs:13
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.
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1806 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:8
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:13
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid. — REDACTED:148
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×2) — REDACTED:8, src/Shopway.App/Program.cs:7
What to do
- Re-enable token validation — `ValidateLifetime` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×3) — src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:45, src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:83, src/Shopway.Persistence/Pipelines/ReferenceValidationPipeline.cs:36
What to do
- Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch
X13 · Undrained process stream
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
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 208/222 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×10) — src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:34, src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:40, src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:51, …
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. (×2) — src/Shopway.Application/Middlewares/ErrorHandlingMiddleware.cs:46, src/Shopway.Persistence/Registration/HealthCheckRegistration.cs:109
- No CancellationToken parameter, and the token `httpRequest.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpRequest.HttpContext.RequestAborted` on, or take a CancellationToken. — src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:125
- 4 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×3) — src/Shopway.Application/Features/Orders/Events/DisplayMessageWhenOrderHeaderCreatedDomainEventHandler.cs:8, src/Shopway.Application/Features/Products/Events/DisplayMessageWhenProductCreatedDomainEventHandler.cs:8, src/Shopway.Application/Features/Products/Events/DisplayMessageWhenReviewAddedDomainEventHandler.cs:8
- Its signature is fixed by the framework, and the token it carries (`context.CancellationToken`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.CancellationToken` to them. — src/Shopway.Persistence/BackgroundJobs/DeleteOutdatedSoftDeletableEntitiesJob.cs:24
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
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
- ~1.0 `!` suppressions per 1k syntax nodes — 256 suppression(s) across the 246658 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Strong | Solid. |
| Architecture | 63% | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Weak — gated by D13, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 83% | Strong | Solid. |
| Event-Driven | 89% | Strong | Solid. |
| Performance | 97% | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- 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 web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- 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 15 — the compose project is invalid) — time="2026-11-08T08:37:04Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T08:37:04Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "portainer" has neither an image nor a build context specified: invalid compose project; 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.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D21 Naming Consistency — D21 withholds its affix on another kind of member (`Is` on a non-bool, `Async` on a non-awaitable) rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 161 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- 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)
- ED5 Idempotency — Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 15 current-state document(s) make no claim of a kind M4 checks. 7 claim(s) of kinds M4 does not check were not checked (path 1, command argument 6); M4 checks only links and versions and artefact counts.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 72 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
- 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/Shopway.Domain/Common/Results/ValidationResult.cs:2
- Namespace dependency cycle src/Shopway.Domain/Users/User.cs:3
- Namespace dependency cycle src/Shopway.Application/Abstractions/ISecurityTokenService.cs:1
- Namespace dependency cycle src/Shopway.Persistence/Framework/UnitOfWork.cs:8
- Namespace dependency cycle src/Shopway.Domain/Common/DataProcessing/Abstractions/IDynamicFilter.cs:5
- Namespace dependency cycle src/Shopway.Domain/Products/ProductKey.cs:2
- Namespace dependency cycle src/Shopway.Application/Abstractions/CQRS/IMediatorProxyService.cs:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:17
- WriteOnlyPrivateField src/Shopway.Application/Features/Users/Commands/RemoveRoleFromUser/RemoveRoleFromUserCommandHandler.cs:17
- WriteOnlyPrivateField REDACTED:32
- WriteOnlyPrivateField test/Shopway.Tests.Unit/UtilityTests/IEntityUtilityTests.cs:12
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/Shopway.Presentation/Shopway.Presentation.csproj:11
- Dual write (no outbox): MimeKitEmailSender.SendEmailAsync src/Shopway.Infrastructure/Services/MimeKitEmailSender.cs:15
Serious — 145 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
- Async method without CancellationToken: HasRolesAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:34
- Async method without CancellationToken: HasPermissionsAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:40
- Async method without CancellationToken: HasPermissionToReadAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:51
- Async method without CancellationToken: HandleExceptionAsync src/Shopway.Application/Middlewares/ErrorHandlingMiddleware.cs:46
- Async method without CancellationToken: GetPaymentGatewayEvent src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:125
- Async method without CancellationToken: Refund src/Shopway.Domain/Orders/OrderHeader.cs:158
- Async method without CancellationToken: Refund src/Shopway.Domain/Orders/Payment.cs:49
- Async method without CancellationToken: WriteResponse src/Shopway.Persistence/Registration/HealthCheckRegistration.cs:109
- Async method without CancellationToken: GetPermissionsAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:15
- Async method without CancellationToken: HasPermissionsAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:39
- Async method without CancellationToken: HasPermissionToReadAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:71
- Async method without CancellationToken: HasRolesAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:88
- Async method without CancellationToken: AddOutboxMessageConsumer src/Shopway.Persistence/Repositories/OutboxRepository.cs:35
- Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:16
- Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:32
- Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:16
- Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:32
- Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.OrderHeaders.cs:11
- Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.Products.cs:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: FluentValidation.AspNetCore REDACTED:10
- Deprecated: xunit test/Shopway.Tests.Unit/Shopway.Tests.Unit.csproj:17
- Deprecated: xunit test/Shopway.Tests.Integration/Shopway.Tests.Integration.csproj:19
- Deprecated: xunit REDACTED:21
- Deprecated: xunit REDACTED:17
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) REDACTED:56
- Duplicated block (13 lines × 2) REDACTED:79
- Duplicated block (13 lines × 2) src/Shopway.Application/Utilities/FluentValidationUtilities.cs:139
- Duplicated block (13 lines × 2) src/Shopway.Application/Features/Proxy/GenericValidators/GenericFluentValidationUtilities.cs:117
- Duplicated block (10 lines × 2) src/Shopway.Application/Cache/ApplicationCache.AllowedFilterOperations.cs:15
- Duplicated block (10 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:43
- Duplicated block (10 lines × 2) PaymentGateway/Cryptography/HashUtilities.cs:10
- Duplicated block (10 lines × 2) src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGroup.cs:13
- Duplicated block (5 lines × 2) src/Shopway.Domain/Orders/OrderLineKeyJsonConverter.cs:48
- Duplicated block (5 lines × 2) src/Shopway.Domain/Products/ValueObjects/ProductName.cs:37
- Duplicated block (5 lines × 2) src/Shopway.Domain/Users/ValueObjects/AccessToken.cs:32
- Duplicated block (5 lines × 2) src/Shopway.Domain/Users/ValueObjects/PasswordHash.cs:33
- Change coupling: ProductOffsetPageQueryHandler.cs ↔ ProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs:1
- Change coupling: ProductOffsetPageQueryHandler.cs ↔ CachedProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs:1
- Change coupling: ProductRepository.cs ↔ SpecificationUtilities.cs src/Shopway.Persistence/Repositories/ProductRepository.cs:1
- Duplicated block (7 lines × 2) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:29
- Duplicated block (7 lines × 2) src/Shopway.Domain/Products/IProductRepository.cs:48
- Duplicated block (7 lines × 2) src/Shopway.Domain/Common/Discriminators/StrategyCacheFactory.cs:16
- Duplicated block (6 lines × 2) src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:10
- Duplicated block (6 lines × 2) PaymentGateway/DummyGatewayTypes/Session.cs:3
- Duplicated block (6 lines × 2) src/Shopway.Domain/Users/ValueObjects/FirstName.cs:41
- Anemic entity: OrderLine src/Shopway.Domain/Orders/OrderLine.cs:7
- Anemic entity: Review src/Shopway.Domain/Products/Review.cs:8
- Anemic entity: Customer src/Shopway.Domain/Users/Customer.cs:8
- Sync-over-async (deadlock risk) through `.Result` src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:45
- Sync-over-async (deadlock risk) through `.Result` src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:83
- Sync-over-async (deadlock risk) through `.Result` src/Shopway.Persistence/Pipelines/ReferenceValidationPipeline.cs:36
- Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Orders/Events/DisplayMessageWhenOrderHeaderCreatedDomainEventHandler.cs:8
- Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Products/Events/DisplayMessageWhenProductCreatedDomainEventHandler.cs:8
- Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Products/Events/DisplayMessageWhenReviewAddedDomainEventHandler.cs:8
- Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore
- Prerelease dependency: OpenTelemetry.Instrumentation.EntityFrameworkCore
- REDACTED
- REDACTED
- Duplicated block (22 lines × 3) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:42
- Duplicated block (22 lines × 3) src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs:44
- Duplicated block (18 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:18
- Duplicated block (18 lines × 2) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:28
- Duplicated block (16 lines × 2) src/Shopway.Application/Features/Users/Commands/LoginByGoogle/LoginByGoogleCommandHandler.cs:61
- Duplicated block (16 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPropertyToReadPermission/AddPropertyToReadPermissionCommandHandler.cs:18
- Low cohesion: Specification (LCOM4 16) src/Shopway.Persistence/Specifications/Specification.cs:44
- Low cohesion: User (LCOM4 5) src/Shopway.Domain/Users/User.cs:9
- One operation mutates 2 aggregates: CachedOrderHeaderRepository.Update src/Shopway.Persistence/Repositories/Decorators/CachedOrderHeaderRepository.cs:58
- One operation mutates 2 aggregates: CachedProductRepository.Update src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:56
- Domain type reads the wall clock: OrderHeader src/Shopway.Domain/Orders/OrderHeader.cs:130
- Domain type reads the wall clock: User src/Shopway.Domain/Users/User.cs:66
- Stateful singleton: WebhookService PaymentGateway/Webhook/WebhookService.cs:8
- StringUtilities.SqlLike (cyclomatic 35) src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166
- CommentedOutCode test/Shopway.Tests.Benchmark/Benchmarks/ReflectionUtilitiesBenchmarks.cs:80
- StringUtilities.SqlLike (cognitive 83) src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166
- FilterByEntryJsonConverter.Read (cognitive 32) src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:12
- MappingEntryJsonConverter.Read (cognitive 26) src/Shopway.Domain/Common/DataProcessing/MappingEntryJsonConverter.cs:10
- ApplicationCache.CreateValidationResultCache (cognitive 19) src/Shopway.Application/Cache/ApplicationCache.ResultValidations.cs:21
- MappingEntry.GetAllPropertyNamesWithHierarchy (cognitive 17) src/Shopway.Domain/Common/DataProcessing/MappingEntry.cs:21
- REDACTED
- TooManyMethods: Error src/Shopway.Domain/Common/Errors/Error.Common.cs
- Change-coupling hub: ProductDictionaryCursorPageQueryHandler.cs → ProductOffsetPageQueryHandler.cs, CachedProductRepository.cs, ProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductDictionaryCursorPageQuery/ProductDictionaryCursorPageQueryHandler.cs
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:41
- Duplicated block (28 lines × 2) src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:21
- Duplicated block (21 lines × 2) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:48
- Duplicated block (15 lines × 2) src/Shopway.Application/Features/Users/Commands/LoginTwoFactorSecondStep/LoginTwoFactorSecondStepCommandHandler.cs:53
- Duplicated block (17 lines × 2) src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:71
- Duplicated block (12 lines × 6) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:44
- Duplicated block (12 lines × 2) src/Shopway.Application/Features/Orders/Commands/AddOrderLine/AddOrderLineCommandValidator.Fluent.cs:11
- Duplicated block (9 lines × 2) SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs:68
- Duplicated block (22 lines × 2) src/Shopway.Application/Abstractions/CursorPageQueryValidator.Fluent.cs:21
- Duplicated block (6 lines × 3) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandValidator.Fluent.cs:11
- Duplicated block (5 lines × 3) src/Shopway.Domain/Products/ValueObjects/Description.cs:32
- Coverage not measured — test suite did not build
- Hollow method — returns a constant without doing the work src/Shopway.Domain/Common/Utilities/IEnumerableUtilities.cs:123
- Empty method body — does nothing with its inputs src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Refunds/RefundService.cs:5
- CI test gate excludes suites by filter REDACTED:29
- No DR/backup evidence
- Token validation disabled REDACTED:148
- NuGet dependencies are not locked
- Async method drops its ambient CancellationToken: Execute src/Shopway.Persistence/BackgroundJobs/DeleteOutdatedSoftDeletableEntitiesJob.cs:24
Minor — 175 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/Shopway.Domain/Common/Utilities/QueryableUtilities.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/Shopway.Persistence/Utilities/QueryableUtilities.cs:1
- Orphaned file src/Shopway.Domain/Common/Utilities/StringUtilities.cs:1
- Orphaned file src/Shopway.Persistence/Specifications/Specification.cs:1
- Orphaned file src/Shopway.Domain/Common/Utilities/ReflectionUtilities.cs:1
- Orphaned file src/Shopway.Domain/Common/Errors/Error.Common.cs:1
- Orphaned file src/Shopway.Domain/Common/DataProcessing/DataTransferObject.cs:1
- Orphaned file src/Shopway.Application/Utilities/FluentValidationUtilities.cs:1
- Orphaned file src/Shopway.Domain/Common/Utilities/ExpressionUtilities.cs:1
- Orphaned file src/Shopway.Persistence/Specifications/SpecificationUtilities.cs:1
- Orphaned file src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:1
- Orphaned file src/Shopway.Application/Features/Proxy/MediatorProxyService.cs:1
- Orphaned file src/Shopway.Infrastructure/Builders/Batch/BatchResponseEntryBuilder.cs:1
- Orphaned file src/Shopway.Infrastructure/Builders/Batch/BatchResponseBuilder.cs:1
- Orphaned file src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:1
- Orphaned file REDACTED:1
- Orphaned file SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdGenerator/EntityIdToGenerateEntry.cs:1
- Orphaned file src/Shopway.Persistence/Repositories/ProductRepository.cs:1
- Orphaned file src/Shopway.Application/Cache/ApplicationCache.ResultValidations.cs:1
- Orphaned file src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandHandler.cs:1
- Orphaned file src/Shopway.Domain/Common/DataProcessing/IncludeBuilder.cs:1
- Orphaned file src/Shopway.Domain/Users/ValueObjects/Address.cs:1
- Orphaned file src/Shopway.Application/Registration/MediatorRegistration.cs:1
- Endpoints outside the guard REDACTED:42
- Endpoints outside the guard REDACTED:58
- Endpoints outside the guard REDACTED:74
- Endpoints outside the guard REDACTED:90
- Endpoints outside the guard REDACTED:119
- Endpoints outside the guard REDACTED:135
- Endpoints outside the guard REDACTED:171
- Endpoints outside the guard REDACTED:188
- Endpoints outside the guard REDACTED:205
- Outdated: FastEndpoints src/Shopway.Presentation/Shopway.Presentation.csproj:21
- Outdated: FastEndpoints.AspVersioning src/Shopway.Presentation/Shopway.Presentation.csproj:22
- Outdated: FastEndpoints.Security src/Shopway.Presentation/Shopway.Presentation.csproj:23
- Outdated: FastEndpoints.Swagger src/Shopway.Presentation/Shopway.Presentation.csproj:24
- Outdated: Scrutor REDACTED:19
- Outdated: Swashbuckle.AspNetCore REDACTED:16
- Outdated: coverlet.collector SourceGenerators/Shopway.SourceGenerator.Base.Tests.Unit/Shopway.SourceGenerator.Base.Tests.Unit.csproj:14
- Outdated: Xunit.DependencyInjection REDACTED:18
- Mutable entity: DataTransferObject src/Shopway.Domain/Common/DataProcessing/DataTransferObject.cs:10
- Mutable entity: OrderHeader src/Shopway.Domain/Orders/OrderHeader.cs:17
- Mutable entity: OrderLine src/Shopway.Domain/Orders/OrderLine.cs:7
- Mutable entity: Payment src/Shopway.Domain/Orders/Payment.cs:13
- Mutable entity: Product src/Shopway.Domain/Products/Product.cs:8
- Mutable entity: Review src/Shopway.Domain/Products/Review.cs:8
- Mutable entity: Customer src/Shopway.Domain/Users/Customer.cs:8
- Mutable entity: User src/Shopway.Domain/Users/User.cs:9
- Commented-out code src/Shopway.Application/Features/Proxy/GenericPageQuery/GenericPageQueryStrategyAttribute.cs:28
- Commented-out code src/Shopway.Application/Features/Proxy/GenericQuery/QueryById/GenericStrategyByIdAttribute.cs:26
- Commented-out code src/Shopway.Application/Features/Proxy/GenericQuery/QueryByKey/GenericStrategyByKeyAttribute.cs:26
- Commented-out code src/Shopway.Domain/Common/Utilities/ReflectionUtilities.cs:248
- Commented-out code src/Shopway.Persistence/Registration/DatabaseContextRegistration.cs:30
- Commented-out code src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:46
- redundant comment REDACTED:24
- redundant comment src/Shopway.Domain/Common/BaseTypes/ValueObject.cs:55
- redundant comment test/Shopway.Tests.Integration.Container/Api/ShopwayApiFactory.cs:36
- No security response headers detected
- No security response headers detected REDACTED:8
- No security response headers detected src/Shopway.App/Program.cs:7
- Projects may be oversized for their cohesion REDACTED:1
- Projects may be oversized for their cohesion REDACTED:1
- REDACTED
- REDACTED
- Duplicated predicate src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:23
- Duplicated predicate src/Shopway.Infrastructure/Registration/ServiceRegistration.cs:72
- Fat interface: IProductRepository (20 members) src/Shopway.Domain/Products/IProductRepository.cs:9
- Partial audit-trail evidence
- Partial data-retention evidence
- ObsoleteWithoutCallers src/Shopway.Persistence/Specifications/Specification.cs:222
- No ADRs found
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- Disabled test test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11
- No ADRs
- Sleep-based test synchronization
- Logging is not universal
- Console output used as the logging channel src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs:13
- No SAST REDACTED:8
- No dependency-update automation REDACTED:13
- No rollback/health safety
- No changelog
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 56 finding(s)
- Outdated: Asp.Versioning.Mvc.ApiExplorer
- Outdated: Microsoft.AspNetCore.Authentication.Google
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Swashbuckle.AspNetCore.Filters
- Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets
- Outdated: FluentValidation.AspNetCore
- Outdated: MediatR
- Outdated: ZiggyCreatures.FusionCache
- Outdated: Google.Apis.Auth.AspNetCore3
- Outdated: MailKit
- Outdated: Polly
- Outdated: SymSpell
- Outdated: System.Linq.Dynamic.Core
- Outdated: Ulid
- Outdated: FluentAssertions
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NSubstitute
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Outdated: Microsoft.Extensions.Configuration
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: RestSharp
- Outdated: Microsoft.AspNetCore.Mvc.Testing
- Outdated: Testcontainers
- doc comments repeat the names src/Shopway.Application/Features/DictionaryResponseEntry.cs:10
- doc comments repeat the names src/Shopway.Domain/Common/BaseTypes/Enumeration.cs:49
- doc comments repeat the names src/Shopway.Persistence/Utilities/QueryableUtilities.cs:59
- doc comments repeat the names REDACTED:30
- doc comments repeat the names test/Shopway.Tests.Integration/Abstractions/ControllerTestBase.cs:59
- doc comments repeat the names test/Shopway.Tests.Integration.Container/Abstractions/ControllerTestBase.cs:32
- doc comments repeat the names test/Shopway.Tests.Unit/Abstractions/TestBase.Products.cs:11
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Skipped (documented): CleanDatabaseFromTestDataAsync test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11
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-1f98138769314f38a55a06c1136db735/history.json --exit-code 0 --source . | 23 | 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-1f98138769314f38a55a06c1136db735/tree.json --exit-code 0 --source . | 8 | 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/Shopway.Persistence/Migrations . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list DomainDrivenDesignUniversity.sln package --vulnerable --include-transitive --format json | 19 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | 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 161 file(s) — `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, … (+156 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5ded83b2492743fcbc95acadcbe6b31f | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 7 field(s)
- LogUserCommand.Email src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommand.cs:7
- LoginTwoFactorFirstStepCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorFirstStep/LoginTwoFactorFirstStepCommand.cs:7
- LoginTwoFactorSecondStepCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorSecondStep/LoginTwoFactorSecondStepCommand.cs:7
- LoginTwoFactorToptCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorTopt/LoginTwoFactorToptCommand.cs:7
- RegisterUserCommand.Email src/Shopway.Application/Features/Users/Commands/RegisterUser/RegisterUserCommand.cs:8
- UserResponse.Email src/Shopway.Application/Features/Users/Queries/GetUserByUsername/UserResponse.cs:10
- User.Email src/Shopway.Domain/Users/User.cs:26
Name — 2 field(s)
- Customer.FirstName src/Shopway.Domain/Users/Customer.cs:40
- Customer.LastName src/Shopway.Domain/Users/Customer.cs:41
Address — 1 field(s)
- Address.ZipCode src/Shopway.Domain/Users/ValueObjects/Address.cs:72
Date of birth — 1 field(s)
- Customer.DateOfBirth src/Shopway.Domain/Users/Customer.cs:46
Phone — 1 field(s)
- Customer.PhoneNumber src/Shopway.Domain/Users/Customer.cs:47