LycheeOrg/Lychee

1→6 Image uses Image.Files part of a loop✕

Connections

2 pairs of types, where a type in Image uses a type in Image.Files.

The types involved

• App.Image.PlaceholderEncoder → App.Image.Files.InMemoryBuffer
• App.Image.StreamStat → App.Image.Files.NativeLocalFile

Direction

Image uses Image.Files, so a change to Image.Files can break Image, while a change to Image can't break Image.Files.

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.

1→11 Image uses Models part of a loop✕

Connections

4 pairs of types, where a type in Image uses a type in Models.

The types involved

• App.Image.PlaceholderEncoder → App.Models.SizeVariant
• App.Image.SizeVariantDefaultFactory → App.Models.Photo
• App.Image.SizeVariantDefaultFactory → App.Models.SizeVariant
• App.Image.Watermarker → App.Models.SizeVariant

Direction

Image uses Models, so a change to Models can break Image, while a change to Image can't break Models.

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.

1→14 Image uses Repositories part of a loop✕

Connections

1 pair of types, where a type in Image uses a type in Repositories.

The types involved

• App.Image.SizeVariantDimensionHelpers → App.Repositories.ConfigManager

Direction

Image uses Repositories, so a change to Repositories can break Image, while a change to Image can't break Repositories.

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.

1→15 Image uses Enum part of a loop✕

Connections

2 pairs of types, where a type in Image uses a type in Enum.

The types involved

• App.Image.SizeVariantDefaultFactory → App.Enum.SizeVariantType
• App.Image.SizeVariantDimensionHelpers → App.Enum.SizeVariantType

Direction

Image uses Enum, so a change to Enum can break Image, while a change to Image can't break Enum.

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.

1→23 Image uses DTO part of a loop✕

Connections

3 pairs of types, where a type in Image uses a type in DTO.

The types involved

• App.Image.CoordinateCalculator → App.DTO.ImageDimension
• App.Image.SizeVariantDefaultFactory → App.DTO.ImageDimension
• App.Image.SizeVariantDimensionHelpers → App.DTO.ImageDimension

Direction

Image uses DTO, so a change to DTO can break Image, while a change to Image can't break DTO.

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.

1→26 Image uses Contracts.Models part of a loop✕

Connections

2 pairs of types, where a type in Image uses a type in Contracts.Models.

The types involved

• App.Image.SizeVariantDefaultFactory → App.Contracts.Models.AbstractSizeVariantNamingStrategy
• App.Image.SizeVariantDefaultFactory → App.Contracts.Models.SizeVariantFactory

Direction

Image uses Contracts.Models, so a change to Contracts.Models can break Image, while a change to Image can't break Contracts.Models.

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.

2→11 Models.Extensions uses Models part of a loop✕

Connections

4 pairs of types, where a type in Models.Extensions uses a type in Models.

The types involved

• App.Models.Extensions.ResolvesUserContext → App.Models.User
• App.Models.Extensions.SizeVariants → App.Models.Photo
• App.Models.Extensions.SizeVariants → App.Models.SizeVariant
• App.Models.Extensions.Thumb → App.Models.Photo

Direction

Models.Extensions uses Models, so a change to Models can break Models.Extensions, while a change to Models.Extensions can't break Models.

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.

2→15 Models.Extensions uses Enum part of a loop✕

Connections

3 pairs of types, where a type in Models.Extensions uses a type in Enum.

The types involved

• App.Models.Extensions.SizeVariants → App.Enum.SizeVariantType
• App.Models.Extensions.SortingDecorator → App.Enum.ColumnSortingType
• App.Models.Extensions.SortingDecorator → App.Enum.OrderSortingType

Direction

Models.Extensions uses Enum, so a change to Enum can break Models.Extensions, while a change to Models.Extensions can't break Enum.

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.

2→23 Models.Extensions uses DTO part of a loop✕

Connections

3 pairs of types, where a type in Models.Extensions uses a type in DTO.

The types involved

• App.Models.Extensions.BaseAlbum → App.DTO.PhotoSortingCriterion
• App.Models.Extensions.SizeVariants → App.DTO.ImageDimension
• App.Models.Extensions.Thumb → App.DTO.SortingCriterion

Direction

Models.Extensions uses DTO, so a change to DTO can break Models.Extensions, while a change to Models.Extensions can't break DTO.

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.

2→26 Models.Extensions uses Contracts.Models part of a loop✕

Connections

2 pairs of types, where a type in Models.Extensions uses a type in Contracts.Models.

The types involved

• App.Models.Extensions.BaseAlbum → App.Contracts.Models.AbstractAlbum
• App.Models.Extensions.BaseAlbum → App.Contracts.Models.HasRandomID

Direction

Models.Extensions uses Contracts.Models, so a change to Contracts.Models can break Models.Extensions, while a change to Models.Extensions can't break Contracts.Models.

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 Policies uses SmartAlbums part of a loop✕

Connections

1 pair of types, where a type in Policies uses a type in SmartAlbums.

The types involved

• App.Policies.AlbumPolicy → App.SmartAlbums.BaseSmartAlbum

Direction

Policies uses SmartAlbums, so a change to SmartAlbums can break Policies, while a change to Policies can't break SmartAlbums.

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→11 Policies uses Models part of a loop✕

Connections

15 pairs of types, where a type in Policies uses a type in Models.

The types involved

• App.Policies.AiVisionPolicy → App.Models.Person
• App.Policies.AiVisionPolicy → App.Models.User
• App.Policies.AlbumPolicy → App.Models.User
• App.Policies.AlbumQueryPolicy → App.Models.User
• App.Policies.BasePolicy → App.Models.User
• App.Policies.MetricsPolicy → App.Models.User
• App.Policies.PhotoPolicy → App.Models.Photo
• App.Policies.PhotoPolicy → App.Models.User
• App.Policies.PhotoQueryPolicy → App.Models.Album
• App.Policies.PhotoQueryPolicy → App.Models.User
• App.Policies.SettingsPolicy → App.Models.User
• App.Policies.TagPolicy → App.Models.User
• App.Policies.UserGroupPolicy → App.Models.User
• App.Policies.UserGroupPolicy → App.Models.UserGroup
• App.Policies.UserPolicy → App.Models.User

Direction

Policies uses Models, so a change to Models can break Policies, while a change to Policies can't break Models.

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→15 Policies uses Enum part of a loop✕

Connections

3 pairs of types, where a type in Policies uses a type in Enum.

The types involved

• App.Policies.AiVisionPolicy → App.Enum.FacePermissionMode
• App.Policies.AlbumPolicy → App.Enum.FacePermissionMode
• App.Policies.PhotoPolicy → App.Enum.FacePermissionMode

Direction

Policies uses Enum, so a change to Enum can break Policies, while a change to Policies can't break Enum.

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→26 Policies uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in Policies uses a type in Contracts.Models.

The types involved

• App.Policies.AlbumPolicy → App.Contracts.Models.AbstractAlbum

Direction

Policies uses Contracts.Models, so a change to Contracts.Models can break Policies, while a change to Policies can't break Contracts.Models.

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→14 Services.Cache uses Repositories part of a loop✕

Connections

1 pair of types, where a type in Services.Cache uses a type in Repositories.

The types involved

• App.Services.Cache.ManagedCacheService → App.Repositories.ConfigManager

Direction

Services.Cache uses Repositories, so a change to Repositories can break Services.Cache, while a change to Services.Cache can't break Repositories.

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→15 Services.Cache uses Enum part of a loop✕

Connections

3 pairs of types, where a type in Services.Cache uses a type in Enum.

The types involved

• App.Services.Cache.CacheKeyProvider → App.Enum.AlbumListingScope
• App.Services.Cache.CacheKeyProvider → App.Enum.ColumnSortingType
• App.Services.Cache.CacheKeyProvider → App.Enum.OrderSortingType

Direction

Services.Cache uses Enum, so a change to Enum can break Services.Cache, while a change to Services.Cache can't break Enum.

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→23 Services.Cache uses DTO part of a loop✕

Connections

2 pairs of types, where a type in Services.Cache uses a type in DTO.

The types involved

• App.Services.Cache.CacheKeyProvider → App.DTO.MapViewport
• App.Services.Cache.CacheKeyProvider → App.DTO.SortingCriterion

Direction

Services.Cache uses DTO, so a change to DTO can break Services.Cache, while a change to Services.Cache can't break DTO.

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→2 Http.Resources.GalleryConfigs uses Models.Extensions✕

Connections

1 pair of types, where a type in Http.Resources.GalleryConfigs uses a type in Models.Extensions.

The types involved

• App.Http.Resources.GalleryConfigs.LandingFeaturedContentResource → App.Models.Extensions.SizeVariants

Direction

Http.Resources.GalleryConfigs uses Models.Extensions, so a change to Models.Extensions can break Http.Resources.GalleryConfigs, while a change to Http.Resources.GalleryConfigs can't break Models.Extensions.

Position

Below the diagonal: Http.Resources.GalleryConfigs uses a module listed above it, which is the healthy direction.

5→11 Http.Resources.GalleryConfigs uses Models part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.GalleryConfigs uses a type in Models.

The types involved

• App.Http.Resources.GalleryConfigs.LandingLinkEmbedResource → App.Models.LandingLink

Direction

Http.Resources.GalleryConfigs uses Models, so a change to Models can break Http.Resources.GalleryConfigs, while a change to Http.Resources.GalleryConfigs can't break Models.

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→14 Http.Resources.GalleryConfigs uses Repositories part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.GalleryConfigs uses a type in Repositories.

The types involved

• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Repositories.ConfigManager

Direction

Http.Resources.GalleryConfigs uses Repositories, so a change to Repositories can break Http.Resources.GalleryConfigs, while a change to Http.Resources.GalleryConfigs can't break Repositories.

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→15 Http.Resources.GalleryConfigs uses Enum part of a loop✕

Connections

33 pairs of types, where a type in Http.Resources.GalleryConfigs uses a type in Enum. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

The types involved

• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Enum.AspectRatioCSSType
• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Enum.ColumnSortingType
• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Enum.PhotoLayoutType
• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Enum.TitleBucketMode
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.AlbumDecorationOrientation
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.AlbumDecorationType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.AlbumHeaderSize
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.AlbumLayoutType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.DateOrderingType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.DefaultAlbumProtectionType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.ImageOverlayType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.PaginationMode
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.PhotoClickAction
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.PhotoHighlightVisibilityType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.PhotoThumbInfoType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.SmallLargeType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.ThumbAlbumSubtitleType
• App.Http.Resources.GalleryConfigs.InitConfig → App.Enum.VisibilityType
• App.Http.Resources.GalleryConfigs.LandingFeaturedContentResource → App.Enum.LandingFeaturedItemType
• App.Http.Resources.GalleryConfigs.LandingLinkEmbedResource → App.Enum.LandingLinkPlacement
• App.Http.Resources.GalleryConfigs.LandingPageResource → App.Enum.LandingAnimationPreset
• App.Http.Resources.GalleryConfigs.LandingPageResource → App.Enum.LandingBackgroundModeType
• App.Http.Resources.GalleryConfigs.LandingPageResource → App.Enum.LandingCtaPosition
• App.Http.Resources.GalleryConfigs.LandingPageResource → App.Enum.LandingFeaturedItemsMode
• App.Http.Resources.GalleryConfigs.LandingPageResource → App.Enum.LandingLayoutType

Direction

Http.Resources.GalleryConfigs uses Enum, so a change to Enum can break Http.Resources.GalleryConfigs, while a change to Http.Resources.GalleryConfigs can't break Enum.

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→26 Http.Resources.GalleryConfigs uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.GalleryConfigs uses a type in Contracts.Models.

The types involved

• App.Http.Resources.GalleryConfigs.AlbumConfig → App.Contracts.Models.AbstractAlbum

Direction

Http.Resources.GalleryConfigs uses Contracts.Models, so a change to Contracts.Models can break Http.Resources.GalleryConfigs, while a change to Http.Resources.GalleryConfigs can't break Contracts.Models.

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.

6→1 Image.Files uses Image✕

Connections

4 pairs of types, where a type in Image.Files uses a type in Image.

The types involved

• App.Image.Files.AbstractBinaryBlob → App.Image.StreamStat
• App.Image.Files.FlysystemFile → App.Image.StreamStat
• App.Image.Files.InMemoryBuffer → App.Image.StreamStat
• App.Image.Files.NativeLocalFile → App.Image.StreamStat

Direction

Image.Files uses Image, so a change to Image can break Image.Files, while a change to Image.Files can't break Image.

Position

Below the diagonal: Image.Files uses a module listed above it, which is the healthy direction.

6→23 Image.Files uses DTO part of a loop✕

Connections

1 pair of types, where a type in Image.Files uses a type in DTO.

The types involved

• App.Image.Files.DownloadedFile → App.DTO.UrlValidatedDTO

Direction

Image.Files uses DTO, so a change to DTO can break Image.Files, while a change to Image.Files can't break DTO.

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.

7→2 SmartAlbums uses Models.Extensions✕

Connections

1 pair of types, where a type in SmartAlbums uses a type in Models.Extensions.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Models.Extensions.Thumb

Direction

SmartAlbums uses Models.Extensions, so a change to Models.Extensions can break SmartAlbums, while a change to SmartAlbums can't break Models.Extensions.

Position

Below the diagonal: SmartAlbums uses a module listed above it, which is the healthy direction.

7→3 SmartAlbums uses Policies✕

Connections

1 pair of types, where a type in SmartAlbums uses a type in Policies.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Policies.PhotoQueryPolicy

Direction

SmartAlbums uses Policies, so a change to Policies can break SmartAlbums, while a change to SmartAlbums can't break Policies.

Position

Below the diagonal: SmartAlbums uses a module listed above it, which is the healthy direction.

7→11 SmartAlbums uses Models part of a loop✕

Connections

2 pairs of types, where a type in SmartAlbums uses a type in Models.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Models.AccessPermission
• App.SmartAlbums.BaseSmartAlbum → App.Models.User

Direction

SmartAlbums uses Models, so a change to Models can break SmartAlbums, while a change to SmartAlbums can't break Models.

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.

7→14 SmartAlbums uses Repositories part of a loop✕

Connections

1 pair of types, where a type in SmartAlbums uses a type in Repositories.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Repositories.ConfigManager

Direction

SmartAlbums uses Repositories, so a change to Repositories can break SmartAlbums, while a change to SmartAlbums can't break Repositories.

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.

7→15 SmartAlbums uses Enum part of a loop✕

Connections

1 pair of types, where a type in SmartAlbums uses a type in Enum.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Enum.SmartAlbumType

Direction

SmartAlbums uses Enum, so a change to Enum can break SmartAlbums, while a change to SmartAlbums can't break Enum.

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.

7→26 SmartAlbums uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in SmartAlbums uses a type in Contracts.Models.

The types involved

• App.SmartAlbums.BaseSmartAlbum → App.Contracts.Models.AbstractAlbum

Direction

SmartAlbums uses Contracts.Models, so a change to Contracts.Models can break SmartAlbums, while a change to SmartAlbums can't break Contracts.Models.

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.

8→2 Http.Resources.Models.Utils uses Models.Extensions✕

Connections

1 pair of types, where a type in Http.Resources.Models.Utils uses a type in Models.Extensions.

The types involved

• App.Http.Resources.Models.Utils.AlbumProtectionPolicy → App.Models.Extensions.BaseAlbum

Direction

Http.Resources.Models.Utils uses Models.Extensions, so a change to Models.Extensions can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break Models.Extensions.

Position

Below the diagonal: Http.Resources.Models.Utils uses a module listed above it, which is the healthy direction.

8→7 Http.Resources.Models.Utils uses SmartAlbums✕

Connections

1 pair of types, where a type in Http.Resources.Models.Utils uses a type in SmartAlbums.

The types involved

• App.Http.Resources.Models.Utils.AlbumProtectionPolicy → App.SmartAlbums.BaseSmartAlbum

Direction

Http.Resources.Models.Utils uses SmartAlbums, so a change to SmartAlbums can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break SmartAlbums.

Position

Below the diagonal: Http.Resources.Models.Utils uses a module listed above it, which is the healthy direction.

8→10 Http.Resources.Models.Utils uses Http.Resources.Models part of a loop✕

Connections

4 pairs of types, where a type in Http.Resources.Models.Utils uses a type in Http.Resources.Models.

The types involved

• App.Http.Resources.Models.Utils.PreFormattedAlbumData → App.Http.Resources.Models.ColourPaletteResource
• App.Http.Resources.Models.Utils.PreformattedPhotoData → App.Http.Resources.Models.SizeVariantResource
• App.Http.Resources.Models.Utils.TimelineData → App.Http.Resources.Models.PhotoResource
• App.Http.Resources.Models.Utils.TimelineData → App.Http.Resources.Models.ThumbAlbumResource

Direction

Http.Resources.Models.Utils uses Http.Resources.Models, so a change to Http.Resources.Models can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break Http.Resources.Models.

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.

8→11 Http.Resources.Models.Utils uses Models part of a loop✕

Connections

3 pairs of types, where a type in Http.Resources.Models.Utils uses a type in Models.

The types involved

• App.Http.Resources.Models.Utils.PersonNameResource → App.Models.Person
• App.Http.Resources.Models.Utils.PreComputedPhotoData → App.Models.Photo
• App.Http.Resources.Models.Utils.PreformattedPhotoData → App.Models.Photo

Direction

Http.Resources.Models.Utils uses Models, so a change to Models can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break Models.

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.

8→15 Http.Resources.Models.Utils uses Enum part of a loop✕

Connections

5 pairs of types, where a type in Http.Resources.Models.Utils uses a type in Enum.

The types involved

• App.Http.Resources.Models.Utils.PreFormattedAlbumData → App.Enum.AlbumTitleColor
• App.Http.Resources.Models.Utils.PreFormattedAlbumData → App.Enum.AlbumTitlePosition
• App.Http.Resources.Models.Utils.TimelineData → App.Enum.ColumnSortingType
• App.Http.Resources.Models.Utils.TimelineData → App.Enum.TimelineAlbumGranularity
• App.Http.Resources.Models.Utils.TimelineData → App.Enum.TimelinePhotoGranularity

Direction

Http.Resources.Models.Utils uses Enum, so a change to Enum can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break Enum.

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.

8→26 Http.Resources.Models.Utils uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.Models.Utils uses a type in Contracts.Models.

The types involved

• App.Http.Resources.Models.Utils.PreFormattedAlbumData → App.Contracts.Models.AbstractAlbum

Direction

Http.Resources.Models.Utils uses Contracts.Models, so a change to Contracts.Models can break Http.Resources.Models.Utils, while a change to Http.Resources.Models.Utils can't break Contracts.Models.

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.

9→5 Http.Resources.V3 uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Resources.V3 uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Resources.V3.AlbumRootConfigResource → App.Http.Resources.GalleryConfigs.RootConfig

Direction

Http.Resources.V3 uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Resources.V3, while a change to Http.Resources.V3 can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Resources.V3 uses a module listed above it, which is the healthy direction.

10→2 Http.Resources.Models uses Models.Extensions✕

Connections

1 pair of types, where a type in Http.Resources.Models uses a type in Models.Extensions.

The types involved

• App.Http.Resources.Models.ThumbResource → App.Models.Extensions.Thumb

Direction

Http.Resources.Models uses Models.Extensions, so a change to Models.Extensions can break Http.Resources.Models, while a change to Http.Resources.Models can't break Models.Extensions.

Position

Below the diagonal: Http.Resources.Models uses a module listed above it, which is the healthy direction.

10→5 Http.Resources.Models uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Resources.Models uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Resources.Models.HeadAbstractAlbumResource → App.Http.Resources.GalleryConfigs.AlbumConfig

Direction

Http.Resources.Models uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Resources.Models, while a change to Http.Resources.Models can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Resources.Models uses a module listed above it, which is the healthy direction.

10→7 Http.Resources.Models uses SmartAlbums✕

Connections

1 pair of types, where a type in Http.Resources.Models uses a type in SmartAlbums.

The types involved

• App.Http.Resources.Models.HeadSmartAlbumResource → App.SmartAlbums.BaseSmartAlbum

Direction

Http.Resources.Models uses SmartAlbums, so a change to SmartAlbums can break Http.Resources.Models, while a change to Http.Resources.Models can't break SmartAlbums.

Position

Below the diagonal: Http.Resources.Models uses a module listed above it, which is the healthy direction.

10→8 Http.Resources.Models uses Http.Resources.Models.Utils✕

Connections

12 pairs of types, where a type in Http.Resources.Models uses a type in Http.Resources.Models.Utils.

The types involved

• App.Http.Resources.Models.HeadAlbumResource → App.Http.Resources.Models.Utils.AlbumProtectionPolicy
• App.Http.Resources.Models.HeadAlbumResource → App.Http.Resources.Models.Utils.PreFormattedAlbumData
• App.Http.Resources.Models.HeadPersonAlbumResource → App.Http.Resources.Models.Utils.AlbumProtectionPolicy
• App.Http.Resources.Models.HeadPersonAlbumResource → App.Http.Resources.Models.Utils.PreFormattedAlbumData
• App.Http.Resources.Models.HeadSmartAlbumResource → App.Http.Resources.Models.Utils.AlbumProtectionPolicy
• App.Http.Resources.Models.HeadSmartAlbumResource → App.Http.Resources.Models.Utils.PreFormattedAlbumData
• App.Http.Resources.Models.HeadTagAlbumResource → App.Http.Resources.Models.Utils.AlbumProtectionPolicy
• App.Http.Resources.Models.HeadTagAlbumResource → App.Http.Resources.Models.Utils.PreFormattedAlbumData
• App.Http.Resources.Models.PhotoResource → App.Http.Resources.Models.Utils.PreComputedPhotoData
• App.Http.Resources.Models.PhotoResource → App.Http.Resources.Models.Utils.PreformattedPhotoData
• App.Http.Resources.Models.PhotoResource → App.Http.Resources.Models.Utils.TimelineData
• App.Http.Resources.Models.ThumbAlbumResource → App.Http.Resources.Models.Utils.TimelineData

Direction

Http.Resources.Models uses Http.Resources.Models.Utils, so a change to Http.Resources.Models.Utils can break Http.Resources.Models, while a change to Http.Resources.Models can't break Http.Resources.Models.Utils.

Position

Below the diagonal: Http.Resources.Models uses a module listed above it, which is the healthy direction.

10→11 Http.Resources.Models uses Models part of a loop✕

Connections

35 pairs of types, where a type in Http.Resources.Models uses a type in Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

The types involved

• App.Http.Resources.Models.AccessPermissionResource → App.Models.AccessPermission
• App.Http.Resources.Models.AlbumStatisticsResource → App.Models.Statistics
• App.Http.Resources.Models.ColourPaletteResource → App.Models.Palette
• App.Http.Resources.Models.ConfigCategoryResource → App.Models.ConfigCategory
• App.Http.Resources.Models.ConfigResource → App.Models.Configs
• App.Http.Resources.Models.ContactMessageResource → App.Models.ContactMessage
• App.Http.Resources.Models.FaceResource → App.Models.Face
• App.Http.Resources.Models.FaceSuggestionResource → App.Models.FaceSuggestion
• App.Http.Resources.Models.HeadAlbumResource → App.Models.Album
• App.Http.Resources.Models.HeadPersonAlbumResource → App.Models.PersonAlbum
• App.Http.Resources.Models.HeadTagAlbumResource → App.Models.TagAlbum
• App.Http.Resources.Models.JobHistoryResource → App.Models.JobHistory
• App.Http.Resources.Models.LandingFeaturedItemResource → App.Models.LandingFeaturedItem
• App.Http.Resources.Models.LandingLinkResource → App.Models.LandingLink
• App.Http.Resources.Models.LightUserResource → App.Models.User
• App.Http.Resources.Models.LiveMetricsResource → App.Models.LiveMetrics
• App.Http.Resources.Models.ModerationEventResource → App.Models.PhotoModerationEvent
• App.Http.Resources.Models.ModerationResource → App.Models.Photo
• App.Http.Resources.Models.NsfwDetectionResource → App.Models.NsfwDetection
• App.Http.Resources.Models.NsfwFindingResource → App.Models.Photo
• App.Http.Resources.Models.PanoramaResource → App.Models.Photo
• App.Http.Resources.Models.PersonResource → App.Models.Person
• App.Http.Resources.Models.PhotoAlbumResource → App.Models.Album
• App.Http.Resources.Models.PhotoFacesResource → App.Models.Photo
• App.Http.Resources.Models.PhotoNsfwDetectionsResource → App.Models.Photo

Direction

Http.Resources.Models uses Models, so a change to Models can break Http.Resources.Models, while a change to Http.Resources.Models can't break Models.

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.

10→14 Http.Resources.Models uses Repositories part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.Models uses a type in Repositories.

The types involved

• App.Http.Resources.Models.PhotoRatingResource → App.Repositories.ConfigManager

Direction

Http.Resources.Models uses Repositories, so a change to Repositories can break Http.Resources.Models, while a change to Http.Resources.Models can't break Repositories.

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.

10→15 Http.Resources.Models uses Enum part of a loop✕

Connections

14 pairs of types, where a type in Http.Resources.Models uses a type in Enum.

The types involved

• App.Http.Resources.Models.LandingFeaturedItemResource → App.Enum.LandingFeaturedItemType
• App.Http.Resources.Models.LandingLinkResource → App.Enum.LandingLinkPlacement
• App.Http.Resources.Models.LiveMetricsResource → App.Enum.MetricsAction
• App.Http.Resources.Models.ModerationEventResource → App.Enum.ModerationEvent
• App.Http.Resources.Models.ModerationEventResource → App.Enum.ModerationSource
• App.Http.Resources.Models.PhotoResource → App.Enum.LicenseType
• App.Http.Resources.Models.RenamerRuleResource → App.Enum.RenamerModeType
• App.Http.Resources.Models.SizeVariantResource → App.Enum.SizeVariantType
• App.Http.Resources.Models.UserManagementResource → App.Enum.UserUploadTrustLevel
• App.Http.Resources.Models.UserMemberGroupResource → App.Enum.UserGroupRole
• App.Http.Resources.Models.UserResource → App.Enum.UserSharedAlbumsVisibility
• App.Http.Resources.Models.WebhookResource → App.Enum.PhotoWebhookEvent
• App.Http.Resources.Models.WebhookResource → App.Enum.WebhookMethod
• App.Http.Resources.Models.WebhookResource → App.Enum.WebhookPayloadFormat

Direction

Http.Resources.Models uses Enum, so a change to Enum can break Http.Resources.Models, while a change to Http.Resources.Models can't break Enum.

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.

10→23 Http.Resources.Models uses DTO part of a loop✕

Connections

3 pairs of types, where a type in Http.Resources.Models uses a type in DTO.

The types involved

• App.Http.Resources.Models.AdminStatsResource → App.DTO.AdminStatsOverview
• App.Http.Resources.Models.AdminUpdateStatusResource → App.DTO.UpdateAvailability
• App.Http.Resources.Models.SecurityAdvisoryResource → App.DTO.SecurityAdvisory

Direction

Http.Resources.Models uses DTO, so a change to DTO can break Http.Resources.Models, while a change to Http.Resources.Models can't break DTO.

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.

10→26 Http.Resources.Models uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in Http.Resources.Models uses a type in Contracts.Models.

The types involved

• App.Http.Resources.Models.ThumbAlbumResource → App.Contracts.Models.AbstractAlbum

Direction

Http.Resources.Models uses Contracts.Models, so a change to Contracts.Models can break Http.Resources.Models, while a change to Http.Resources.Models can't break Contracts.Models.

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→2 Models uses Models.Extensions✕

Connections

5 pairs of types, where a type in Models uses a type in Models.Extensions.

The types involved

• App.Models.Album → App.Models.Extensions.BaseAlbum
• App.Models.PersonAlbum → App.Models.Extensions.BaseAlbum
• App.Models.PersonAlbum → App.Models.Extensions.Thumb
• App.Models.TagAlbum → App.Models.Extensions.BaseAlbum
• App.Models.TagAlbum → App.Models.Extensions.Thumb

Direction

Models uses Models.Extensions, so a change to Models.Extensions can break Models, while a change to Models can't break Models.Extensions.

Position

Below the diagonal: Models uses a module listed above it, which is the healthy direction.

11→6 Models uses Image.Files✕

Connections

1 pair of types, where a type in Models uses a type in Image.Files.

The types involved

• App.Models.SizeVariant → App.Image.Files.FlysystemFile

Direction

Models uses Image.Files, so a change to Image.Files can break Models, while a change to Models can't break Image.Files.

Position

Below the diagonal: Models uses a module listed above it, which is the healthy direction.

11→10 Models uses Http.Resources.Models✕

Connections

1 pair of types, where a type in Models uses a type in Http.Resources.Models.

The types involved

• App.Models.SizeVariant → App.Http.Resources.Models.SizeVariantResource

Direction

Models uses Http.Resources.Models, so a change to Http.Resources.Models can break Models, while a change to Models can't break Http.Resources.Models.

Position

Below the diagonal: Models uses a module listed above it, which is the healthy direction.

11→15 Models uses Enum part of a loop✕

Connections

9 pairs of types, where a type in Models uses a type in Enum.

The types involved

• App.Models.Album → App.Enum.AspectRatioType
• App.Models.Album → App.Enum.LicenseType
• App.Models.Album → App.Enum.TimelineAlbumGranularity
• App.Models.BaseAlbumImpl → App.Enum.PhotoLayoutType
• App.Models.BaseAlbumImpl → App.Enum.TimelinePhotoGranularity
• App.Models.Photo → App.Enum.LicenseType
• App.Models.Purchasable → App.Enum.PurchasableLicenseType
• App.Models.Purchasable → App.Enum.PurchasableSizeVariantType
• App.Models.Webhook → App.Enum.PhotoWebhookEvent

Direction

Models uses Enum, so a change to Enum can break Models, while a change to Models can't break Enum.

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→23 Models uses DTO part of a loop✕

Connections

2 pairs of types, where a type in Models uses a type in DTO.

The types involved

• App.Models.Album → App.DTO.AlbumSortingCriterion
• App.Models.BaseAlbumImpl → App.DTO.PhotoSortingCriterion

Direction

Models uses DTO, so a change to DTO can break Models, while a change to Models can't break DTO.

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→26 Models uses Contracts.Models part of a loop✕

Connections

3 pairs of types, where a type in Models uses a type in Contracts.Models.

The types involved

• App.Models.BaseAlbumImpl → App.Contracts.Models.HasRandomID
• App.Models.BaseAlbumImpl → App.Contracts.Models.HasUTCBasedTimes
• App.Models.Photo → App.Contracts.Models.HasUTCBasedTimes

Direction

Models uses Contracts.Models, so a change to Contracts.Models can break Models, while a change to Models can't break Contracts.Models.

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.

12→11 Contracts.PhotoCreate uses Models✕

Connections

1 pair of types, where a type in Contracts.PhotoCreate uses a type in Models.

The types involved

• App.Contracts.PhotoCreate.PhotoDTO → App.Models.Photo

Direction

Contracts.PhotoCreate uses Models, so a change to Models can break Contracts.PhotoCreate, while a change to Contracts.PhotoCreate can't break Models.

Position

Below the diagonal: Contracts.PhotoCreate uses a module listed above it, which is the healthy direction.

12→16 Contracts.PhotoCreate uses DTO.PhotoCreate part of a loop✕

Connections

5 pairs of types, where a type in Contracts.PhotoCreate uses a type in DTO.PhotoCreate.

The types involved

• App.Contracts.PhotoCreate.DuplicatePipe → App.DTO.PhotoCreate.DuplicateDTO
• App.Contracts.PhotoCreate.InitPipe → App.DTO.PhotoCreate.InitDTO
• App.Contracts.PhotoCreate.PhotoPartnerPipe → App.DTO.PhotoCreate.PhotoPartnerDTO
• App.Contracts.PhotoCreate.StandalonePipe → App.DTO.PhotoCreate.StandaloneDTO
• App.Contracts.PhotoCreate.VideoPartnerPipe → App.DTO.PhotoCreate.VideoPartnerDTO

Direction

Contracts.PhotoCreate uses DTO.PhotoCreate, so a change to DTO.PhotoCreate can break Contracts.PhotoCreate, while a change to Contracts.PhotoCreate can't break DTO.PhotoCreate.

Position

Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.

13→3 Services uses Policies✕

Connections

1 pair of types, where a type in Services uses a type in Policies.

The types involved

• App.Services.PersonAlbumMatcher → App.Policies.PhotoQueryPolicy

Direction

Services uses Policies, so a change to Policies can break Services, while a change to Services can't break Policies.

Position

Below the diagonal: Services uses a module listed above it, which is the healthy direction.

13→11 Services uses Models✕

Connections

4 pairs of types, where a type in Services uses a type in Models.

The types involved

• App.Services.AlbumBucketComputer → App.Models.Album
• App.Services.PersonAlbumMatcher → App.Models.PersonAlbum
• App.Services.PersonAlbumMatcher → App.Models.User
• App.Services.PhotoBucketComputer → App.Models.Photo

Direction

Services uses Models, so a change to Models can break Services, while a change to Services can't break Models.

Position

Below the diagonal: Services uses a module listed above it, which is the healthy direction.

13→14 Services uses Repositories part of a loop✕

Connections

9 pairs of types, where a type in Services uses a type in Repositories.

The types involved

• App.Services.AlbumBucketComputer → App.Repositories.ConfigManager
• App.Services.BucketScheme → App.Repositories.ConfigManager
• App.Services.GalleryLockState → App.Repositories.ConfigManager
• App.Services.ModerationHistory → App.Repositories.ConfigManager
• App.Services.MoneyService → App.Repositories.ConfigManager
• App.Services.PersonAlbumMatcher → App.Repositories.ConfigManager
• App.Services.PhotoBucketComputer → App.Repositories.ConfigManager
• App.Services.UrlGenerator → App.Repositories.ConfigManager
• App.Services.UrlValidation → App.Repositories.ConfigManager

Direction

Services uses Repositories, so a change to Repositories can break Services, while a change to Services can't break Repositories.

Position

Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.

13→15 Services uses Enum part of a loop✕

Connections

12 pairs of types, where a type in Services uses a type in Enum.

The types involved

• App.Services.AlbumBucketComputer → App.Enum.ColumnSortingType
• App.Services.AlbumBucketComputer → App.Enum.TimelineAlbumGranularity
• App.Services.BucketKeyWriter → App.Enum.ColumnSortingType
• App.Services.BucketScheme → App.Enum.ColumnSortingType
• App.Services.BucketScheme → App.Enum.OrderSortingType
• App.Services.BucketScheme → App.Enum.TimelineAlbumGranularity
• App.Services.BucketScheme → App.Enum.TimelinePhotoGranularity
• App.Services.ModerationHistory → App.Enum.ModerationEvent
• App.Services.ModerationHistory → App.Enum.ModerationSource
• App.Services.PhotoBucketComputer → App.Enum.ColumnSortingType
• App.Services.PhotoBucketComputer → App.Enum.TimelinePhotoGranularity
• App.Services.UrlGenerator → App.Enum.SizeVariantType

Direction

Services uses Enum, so a change to Enum can break Services, while a change to Services can't break Enum.

Position

Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.

13→23 Services uses DTO part of a loop✕

Connections

4 pairs of types, where a type in Services uses a type in DTO.

The types involved

• App.Services.AdminStatsService → App.DTO.AdminStatsOverview
• App.Services.TitleSplitter → App.DTO.TitleSplitResult
• App.Services.UrlValidation → App.DTO.UrlValidatedDTO
• App.Services.VersionRangeChecker → App.DTO.Version

Direction

Services uses DTO, so a change to DTO can break Services, while a change to Services can't break DTO.

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.

14→3 Repositories uses Policies✕

Connections

1 pair of types, where a type in Repositories uses a type in Policies.

The types involved

• App.Repositories.AlbumRepository → App.Policies.AlbumQueryPolicy

Direction

Repositories uses Policies, so a change to Policies can break Repositories, while a change to Repositories can't break Policies.

Position

Below the diagonal: Repositories uses a module listed above it, which is the healthy direction.

14→4 Repositories uses Services.Cache✕

Connections

2 pairs of types, where a type in Repositories uses a type in Services.Cache.

The types involved

• App.Repositories.AlbumRepository → App.Services.Cache.CacheKeyProvider
• App.Repositories.AlbumRepository → App.Services.Cache.ManagedCacheService

Direction

Repositories uses Services.Cache, so a change to Services.Cache can break Repositories, while a change to Repositories can't break Services.Cache.

Position

Below the diagonal: Repositories uses a module listed above it, which is the healthy direction.

14→11 Repositories uses Models✕

Connections

2 pairs of types, where a type in Repositories uses a type in Models.

The types involved

• App.Repositories.AlbumRepository → App.Models.PersonAlbum
• App.Repositories.AlbumRepository → App.Models.TagAlbum

Direction

Repositories uses Models, so a change to Models can break Repositories, while a change to Repositories can't break Models.

Position

Below the diagonal: Repositories uses a module listed above it, which is the healthy direction.

14→13 Repositories uses Services✕

Connections

1 pair of types, where a type in Repositories uses a type in Services.

The types involved

• App.Repositories.AlbumRepository → App.Services.PersonAlbumMatcher

Direction

Repositories uses Services, so a change to Services can break Repositories, while a change to Repositories can't break Services.

Position

Below the diagonal: Repositories uses a module listed above it, which is the healthy direction.

14→23 Repositories uses DTO part of a loop✕

Connections

2 pairs of types, where a type in Repositories uses a type in DTO.

The types involved

• App.Repositories.AlbumRepository → App.DTO.AlbumSortingCriterion
• App.Repositories.PhotoRepository → App.DTO.PhotoSortingCriterion

Direction

Repositories uses DTO, so a change to DTO can break Repositories, while a change to Repositories can't break DTO.

Position

Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.

15→14 Enum uses Repositories✕

Connections

1 pair of types, where a type in Enum uses a type in Repositories.

The types involved

• App.Enum.SmartAlbumType → App.Repositories.ConfigManager

Direction

Enum uses Repositories, so a change to Repositories can break Enum, while a change to Enum can't break Repositories.

Position

Below the diagonal: Enum uses a module listed above it, which is the healthy direction.

16→6 DTO.PhotoCreate uses Image.Files✕

Connections

4 pairs of types, where a type in DTO.PhotoCreate uses a type in Image.Files.

The types involved

• App.DTO.PhotoCreate.InitDTO → App.Image.Files.NativeLocalFile
• App.DTO.PhotoCreate.StandaloneDTO → App.Image.Files.FlysystemFile
• App.DTO.PhotoCreate.StandaloneDTO → App.Image.Files.NativeLocalFile
• App.DTO.PhotoCreate.VideoPartnerDTO → App.Image.Files.BaseMediaFile

Direction

DTO.PhotoCreate uses Image.Files, so a change to Image.Files can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break Image.Files.

Position

Below the diagonal: DTO.PhotoCreate uses a module listed above it, which is the healthy direction.

16→11 DTO.PhotoCreate uses Models✕

Connections

4 pairs of types, where a type in DTO.PhotoCreate uses a type in Models.

The types involved

• App.DTO.PhotoCreate.DuplicateDTO → App.Models.Photo
• App.DTO.PhotoCreate.PhotoPartnerDTO → App.Models.Photo
• App.DTO.PhotoCreate.StandaloneDTO → App.Models.Photo
• App.DTO.PhotoCreate.VideoPartnerDTO → App.Models.Photo

Direction

DTO.PhotoCreate uses Models, so a change to Models can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break Models.

Position

Below the diagonal: DTO.PhotoCreate uses a module listed above it, which is the healthy direction.

16→12 DTO.PhotoCreate uses Contracts.PhotoCreate✕

Connections

4 pairs of types, where a type in DTO.PhotoCreate uses a type in Contracts.PhotoCreate.

The types involved

• App.DTO.PhotoCreate.DuplicateDTO → App.Contracts.PhotoCreate.PhotoDTO
• App.DTO.PhotoCreate.PhotoPartnerDTO → App.Contracts.PhotoCreate.PhotoDTO
• App.DTO.PhotoCreate.StandaloneDTO → App.Contracts.PhotoCreate.PhotoDTO
• App.DTO.PhotoCreate.VideoPartnerDTO → App.Contracts.PhotoCreate.PhotoDTO

Direction

DTO.PhotoCreate uses Contracts.PhotoCreate, so a change to Contracts.PhotoCreate can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break Contracts.PhotoCreate.

Position

Below the diagonal: DTO.PhotoCreate uses a module listed above it, which is the healthy direction.

16→15 DTO.PhotoCreate uses Enum✕

Connections

2 pairs of types, where a type in DTO.PhotoCreate uses a type in Enum.

The types involved

• App.DTO.PhotoCreate.InitDTO → App.Enum.UserUploadTrustLevel
• App.DTO.PhotoCreate.StandaloneDTO → App.Enum.UserUploadTrustLevel

Direction

DTO.PhotoCreate uses Enum, so a change to Enum can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break Enum.

Position

Below the diagonal: DTO.PhotoCreate uses a module listed above it, which is the healthy direction.

16→23 DTO.PhotoCreate uses DTO part of a loop✕

Connections

2 pairs of types, where a type in DTO.PhotoCreate uses a type in DTO.

The types involved

• App.DTO.PhotoCreate.InitDTO → App.DTO.ImportMode
• App.DTO.PhotoCreate.InitDTO → App.DTO.ImportParam

Direction

DTO.PhotoCreate uses DTO, so a change to DTO can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break DTO.

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.

16→26 DTO.PhotoCreate uses Contracts.Models part of a loop✕

Connections

4 pairs of types, where a type in DTO.PhotoCreate uses a type in Contracts.Models.

The types involved

• App.DTO.PhotoCreate.DuplicateDTO → App.Contracts.Models.AbstractAlbum
• App.DTO.PhotoCreate.InitDTO → App.Contracts.Models.AbstractAlbum
• App.DTO.PhotoCreate.StandaloneDTO → App.Contracts.Models.AbstractAlbum
• App.DTO.PhotoCreate.StandaloneDTO → App.Contracts.Models.AbstractSizeVariantNamingStrategy

Direction

DTO.PhotoCreate uses Contracts.Models, so a change to Contracts.Models can break DTO.PhotoCreate, while a change to DTO.PhotoCreate can't break Contracts.Models.

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.

17→2 Factories uses Models.Extensions✕

Connections

1 pair of types, where a type in Factories uses a type in Models.Extensions.

The types involved

• App.Factories.AlbumFactory → App.Models.Extensions.BaseAlbum

Direction

Factories uses Models.Extensions, so a change to Models.Extensions can break Factories, while a change to Factories can't break Models.Extensions.

Position

Below the diagonal: Factories uses a module listed above it, which is the healthy direction.

17→7 Factories uses SmartAlbums✕

Connections

1 pair of types, where a type in Factories uses a type in SmartAlbums.

The types involved

• App.Factories.AlbumFactory → App.SmartAlbums.BaseSmartAlbum

Direction

Factories uses SmartAlbums, so a change to SmartAlbums can break Factories, while a change to Factories can't break SmartAlbums.

Position

Below the diagonal: Factories uses a module listed above it, which is the healthy direction.

17→11 Factories uses Models✕

Connections

1 pair of types, where a type in Factories uses a type in Models.

The types involved

• App.Factories.PersonFactory → App.Models.Person

Direction

Factories uses Models, so a change to Models can break Factories, while a change to Factories can't break Models.

Position

Below the diagonal: Factories uses a module listed above it, which is the healthy direction.

17→14 Factories uses Repositories✕

Connections

2 pairs of types, where a type in Factories uses a type in Repositories.

The types involved

• App.Factories.AlbumFactory → App.Repositories.ConfigManager
• App.Factories.PersonFactory → App.Repositories.ConfigManager

Direction

Factories uses Repositories, so a change to Repositories can break Factories, while a change to Factories can't break Repositories.

Position

Below the diagonal: Factories uses a module listed above it, which is the healthy direction.

17→15 Factories uses Enum✕

Connections

2 pairs of types, where a type in Factories uses a type in Enum.

The types involved

• App.Factories.AlbumFactory → App.Enum.SmartAlbumType
• App.Factories.OmnipayFactory → App.Enum.OmnipayProviderType

Direction

Factories uses Enum, so a change to Enum can break Factories, while a change to Factories can't break Enum.

Position

Below the diagonal: Factories uses a module listed above it, which is the healthy direction.

17→26 Factories uses Contracts.Models part of a loop✕

Connections

1 pair of types, where a type in Factories uses a type in Contracts.Models.

The types involved

• App.Factories.AlbumFactory → App.Contracts.Models.AbstractAlbum

Direction

Factories uses Contracts.Models, so a change to Contracts.Models can break Factories, while a change to Factories can't break Contracts.Models.

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.

18→4 Listeners uses Services.Cache✕

Connections

10 pairs of types, where a type in Listeners uses a type in Services.Cache.

The types involved

• App.Listeners.ManagedCacheAlbumListingInvalidator → App.Services.Cache.CacheKeyProvider
• App.Listeners.ManagedCacheAlbumListingInvalidator → App.Services.Cache.ManagedCacheService
• App.Listeners.ManagedCacheMapListingInvalidator → App.Services.Cache.CacheKeyProvider
• App.Listeners.ManagedCacheMapListingInvalidator → App.Services.Cache.ManagedCacheService
• App.Listeners.ManagedCachePhotoListingInvalidator → App.Services.Cache.CacheKeyProvider
• App.Listeners.ManagedCachePhotoListingInvalidator → App.Services.Cache.ManagedCacheService
• App.Listeners.ManagedCacheSearchListingInvalidator → App.Services.Cache.CacheKeyProvider
• App.Listeners.ManagedCacheSearchListingInvalidator → App.Services.Cache.ManagedCacheService
• App.Listeners.ManagedCacheUserListingInvalidator → App.Services.Cache.CacheKeyProvider
• App.Listeners.ManagedCacheUserListingInvalidator → App.Services.Cache.ManagedCacheService

Direction

Listeners uses Services.Cache, so a change to Services.Cache can break Listeners, while a change to Listeners can't break Services.Cache.

Position

Below the diagonal: Listeners uses a module listed above it, which is the healthy direction.

18→11 Listeners uses Models✕

Connections

2 pairs of types, where a type in Listeners uses a type in Models.

The types involved

• App.Listeners.OrderCompletedListener → App.Models.Order
• App.Listeners.WebhookListener → App.Models.Photo

Direction

Listeners uses Models, so a change to Models can break Listeners, while a change to Listeners can't break Models.

Position

Below the diagonal: Listeners uses a module listed above it, which is the healthy direction.

18→13 Listeners uses Services✕

Connections

1 pair of types, where a type in Listeners uses a type in Services.

The types involved

• App.Listeners.ManagedCachePhotoListingInvalidator → App.Services.PhotoBucketComputer

Direction

Listeners uses Services, so a change to Services can break Listeners, while a change to Listeners can't break Services.

Position

Below the diagonal: Listeners uses a module listed above it, which is the healthy direction.

18→14 Listeners uses Repositories✕

Connections

1 pair of types, where a type in Listeners uses a type in Repositories.

The types involved

• App.Listeners.ManagedCachePhotoListingInvalidator → App.Repositories.ConfigManager

Direction

Listeners uses Repositories, so a change to Repositories can break Listeners, while a change to Listeners can't break Repositories.

Position

Below the diagonal: Listeners uses a module listed above it, which is the healthy direction.

18→15 Listeners uses Enum✕

Connections

1 pair of types, where a type in Listeners uses a type in Enum.

The types involved

• App.Listeners.WebhookListener → App.Enum.PhotoWebhookEvent

Direction

Listeners uses Enum, so a change to Enum can break Listeners, while a change to Listeners can't break Enum.

Position

Below the diagonal: Listeners uses a module listed above it, which is the healthy direction.

19→11 Services.Image uses Models✕

Connections

1 pair of types, where a type in Services.Image uses a type in Models.

The types involved

• App.Services.Image.NsfwActionService → App.Models.Photo

Direction

Services.Image uses Models, so a change to Models can break Services.Image, while a change to Services.Image can't break Models.

Position

Below the diagonal: Services.Image uses a module listed above it, which is the healthy direction.

19→13 Services.Image uses Services✕

Connections

1 pair of types, where a type in Services.Image uses a type in Services.

The types involved

• App.Services.Image.NsfwActionService → App.Services.ModerationHistory

Direction

Services.Image uses Services, so a change to Services can break Services.Image, while a change to Services.Image can't break Services.

Position

Below the diagonal: Services.Image uses a module listed above it, which is the healthy direction.

19→14 Services.Image uses Repositories✕

Connections

3 pairs of types, where a type in Services.Image uses a type in Repositories.

The types involved

• App.Services.Image.FileExtensionService → App.Repositories.ConfigManager
• App.Services.Image.NsfwActionService → App.Repositories.ConfigManager
• App.Services.Image.NsfwDetectionService → App.Repositories.ConfigManager

Direction

Services.Image uses Repositories, so a change to Repositories can break Services.Image, while a change to Services.Image can't break Repositories.

Position

Below the diagonal: Services.Image uses a module listed above it, which is the healthy direction.

19→15 Services.Image uses Enum✕

Connections

2 pairs of types, where a type in Services.Image uses a type in Enum.

The types involved

• App.Services.Image.NsfwActionService → App.Enum.NsfwBlockFindingAction
• App.Services.Image.NsfwActionService → App.Enum.UserUploadTrustLevel

Direction

Services.Image uses Enum, so a change to Enum can break Services.Image, while a change to Services.Image can't break Enum.

Position

Below the diagonal: Services.Image uses a module listed above it, which is the healthy direction.

20→3 Actions.Shop uses Policies✕

Connections

1 pair of types, where a type in Actions.Shop uses a type in Policies.

The types involved

• App.Actions.Shop.BasketService → App.Policies.AlbumQueryPolicy

Direction

Actions.Shop uses Policies, so a change to Policies can break Actions.Shop, while a change to Actions.Shop can't break Policies.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→11 Actions.Shop uses Models✕

Connections

15 pairs of types, where a type in Actions.Shop uses a type in Models.

The types involved

• App.Actions.Shop.BasketService → App.Models.Album
• App.Actions.Shop.BasketService → App.Models.Order
• App.Actions.Shop.BasketService → App.Models.Photo
• App.Actions.Shop.BasketService → App.Models.PixelSize
• App.Actions.Shop.BasketService → App.Models.PrintSize
• App.Actions.Shop.BasketService → App.Models.User
• App.Actions.Shop.CheckoutService → App.Models.Order
• App.Actions.Shop.OrderService → App.Models.Order
• App.Actions.Shop.OrderService → App.Models.Photo
• App.Actions.Shop.OrderService → App.Models.PixelSize
• App.Actions.Shop.OrderService → App.Models.PrintSize
• App.Actions.Shop.OrderService → App.Models.User
• App.Actions.Shop.PurchasableService → App.Models.Album
• App.Actions.Shop.PurchasableService → App.Models.Photo
• App.Actions.Shop.PurchasableService → App.Models.Purchasable

Direction

Actions.Shop uses Models, so a change to Models can break Actions.Shop, while a change to Actions.Shop can't break Models.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→13 Actions.Shop uses Services✕

Connections

1 pair of types, where a type in Actions.Shop uses a type in Services.

The types involved

• App.Actions.Shop.CheckoutService → App.Services.MoneyService

Direction

Actions.Shop uses Services, so a change to Services can break Actions.Shop, while a change to Actions.Shop can't break Services.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→14 Actions.Shop uses Repositories✕

Connections

1 pair of types, where a type in Actions.Shop uses a type in Repositories.

The types involved

• App.Actions.Shop.OrderService → App.Repositories.ConfigManager

Direction

Actions.Shop uses Repositories, so a change to Repositories can break Actions.Shop, while a change to Actions.Shop can't break Repositories.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→15 Actions.Shop uses Enum✕

Connections

5 pairs of types, where a type in Actions.Shop uses a type in Enum.

The types involved

• App.Actions.Shop.BasketService → App.Enum.PurchasableLicenseType
• App.Actions.Shop.BasketService → App.Enum.PurchasableSizeVariantType
• App.Actions.Shop.CheckoutService → App.Enum.OmnipayProviderType
• App.Actions.Shop.OrderService → App.Enum.PurchasableLicenseType
• App.Actions.Shop.OrderService → App.Enum.PurchasableSizeVariantType

Direction

Actions.Shop uses Enum, so a change to Enum can break Actions.Shop, while a change to Actions.Shop can't break Enum.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→17 Actions.Shop uses Factories✕

Connections

1 pair of types, where a type in Actions.Shop uses a type in Factories.

The types involved

• App.Actions.Shop.CheckoutService → App.Factories.OmnipayFactory

Direction

Actions.Shop uses Factories, so a change to Factories can break Actions.Shop, while a change to Actions.Shop can't break Factories.

Position

Below the diagonal: Actions.Shop uses a module listed above it, which is the healthy direction.

20→23 Actions.Shop uses DTO part of a loop✕

Connections

1 pair of types, where a type in Actions.Shop uses a type in DTO.

The types involved

• App.Actions.Shop.CheckoutService → App.DTO.CheckoutDTO

Direction

Actions.Shop uses DTO, so a change to DTO can break Actions.Shop, while a change to Actions.Shop can't break DTO.

Position

Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.

21→17 Http.Requests uses Factories✕

Connections

1 pair of types, where a type in Http.Requests uses a type in Factories.

The types involved

• App.Http.Requests.BaseApiRequest → App.Factories.AlbumFactory

Direction

Http.Requests uses Factories, so a change to Factories can break Http.Requests, while a change to Http.Requests can't break Factories.

Position

Below the diagonal: Http.Requests uses a module listed above it, which is the healthy direction.

22→3 Actions.Photo uses Policies✕

Connections

1 pair of types, where a type in Actions.Photo uses a type in Policies.

The types involved

• App.Actions.Photo.Timeline → App.Policies.PhotoQueryPolicy

Direction

Actions.Photo uses Policies, so a change to Policies can break Actions.Photo, while a change to Actions.Photo can't break Policies.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→6 Actions.Photo uses Image.Files✕

Connections

2 pairs of types, where a type in Actions.Photo uses a type in Image.Files.

The types involved

• App.Actions.Photo.Create → App.Image.Files.NativeLocalFile
• App.Actions.Photo.Rotate → App.Image.Files.FlysystemFile

Direction

Actions.Photo uses Image.Files, so a change to Image.Files can break Actions.Photo, while a change to Actions.Photo can't break Image.Files.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→11 Actions.Photo uses Models✕

Connections

7 pairs of types, where a type in Actions.Photo uses a type in Models.

The types involved

• App.Actions.Photo.BaseArchive → App.Models.Photo
• App.Actions.Photo.Create → App.Models.Photo
• App.Actions.Photo.MoveOrDuplicate → App.Models.Album
• App.Actions.Photo.Rating → App.Models.Photo
• App.Actions.Photo.Rating → App.Models.User
• App.Actions.Photo.Rotate → App.Models.Photo
• App.Actions.Photo.Timeline → App.Models.Photo

Direction

Actions.Photo uses Models, so a change to Models can break Actions.Photo, while a change to Actions.Photo can't break Models.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→14 Actions.Photo uses Repositories✕

Connections

1 pair of types, where a type in Actions.Photo uses a type in Repositories.

The types involved

• App.Actions.Photo.Timeline → App.Repositories.ConfigManager

Direction

Actions.Photo uses Repositories, so a change to Repositories can break Actions.Photo, while a change to Actions.Photo can't break Repositories.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→15 Actions.Photo uses Enum✕

Connections

4 pairs of types, where a type in Actions.Photo uses a type in Enum.

The types involved

• App.Actions.Photo.BaseArchive → App.Enum.DownloadVariantType
• App.Actions.Photo.Create → App.Enum.UserUploadTrustLevel
• App.Actions.Photo.Rotate → App.Enum.StorageDiskType
• App.Actions.Photo.Timeline → App.Enum.TimelinePhotoGranularity

Direction

Actions.Photo uses Enum, so a change to Enum can break Actions.Photo, while a change to Actions.Photo can't break Enum.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→16 Actions.Photo uses DTO.PhotoCreate✕

Connections

1 pair of types, where a type in Actions.Photo uses a type in DTO.PhotoCreate.

The types involved

• App.Actions.Photo.Create → App.DTO.PhotoCreate.InitDTO

Direction

Actions.Photo uses DTO.PhotoCreate, so a change to DTO.PhotoCreate can break Actions.Photo, while a change to Actions.Photo can't break DTO.PhotoCreate.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→20 Actions.Photo uses Actions.Shop✕

Connections

2 pairs of types, where a type in Actions.Photo uses a type in Actions.Shop.

The types involved

• App.Actions.Photo.Delete → App.Actions.Shop.PurchasableService
• App.Actions.Photo.MoveOrDuplicate → App.Actions.Shop.PurchasableService

Direction

Actions.Photo uses Actions.Shop, so a change to Actions.Shop can break Actions.Photo, while a change to Actions.Photo can't break Actions.Shop.

Position

Below the diagonal: Actions.Photo uses a module listed above it, which is the healthy direction.

22→23 Actions.Photo uses DTO part of a loop✕

Connections

4 pairs of types, where a type in Actions.Photo uses a type in DTO.

The types involved

• App.Actions.Photo.BaseArchive → App.DTO.ChunkSlice
• App.Actions.Photo.BaseArchive → App.DTO.ZippablePhoto
• App.Actions.Photo.Create → App.DTO.ImportMode
• App.Actions.Photo.Create → App.DTO.ImportParam

Direction

Actions.Photo uses DTO, so a change to DTO can break Actions.Photo, while a change to Actions.Photo can't break DTO.

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.

22→26 Actions.Photo uses Contracts.Models part of a loop✕

Connections

3 pairs of types, where a type in Actions.Photo uses a type in Contracts.Models.

The types involved

• App.Actions.Photo.Create → App.Contracts.Models.AbstractAlbum
• App.Actions.Photo.MoveOrDuplicate → App.Contracts.Models.AbstractAlbum
• App.Actions.Photo.Rotate → App.Contracts.Models.AbstractSizeVariantNamingStrategy

Direction

Actions.Photo uses Contracts.Models, so a change to Contracts.Models can break Actions.Photo, while a change to Actions.Photo can't break Contracts.Models.

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→11 DTO uses Models✕

Connections

2 pairs of types, where a type in DTO uses a type in Models.

The types involved

• App.DTO.FolderNode → App.Models.Album
• App.DTO.ImportDTO → App.Models.Album

Direction

DTO uses Models, so a change to Models can break DTO, while a change to DTO can't break Models.

Position

Below the diagonal: DTO uses a module listed above it, which is the healthy direction.

23→15 DTO uses Enum✕

Connections

19 pairs of types, where a type in DTO uses a type in Enum.

The types involved

• App.DTO.BulkAlbumPatchData → App.Enum.AspectRatioType
• App.DTO.BulkAlbumPatchData → App.Enum.ColumnSortingAlbumType
• App.DTO.BulkAlbumPatchData → App.Enum.ColumnSortingPhotoType
• App.DTO.BulkAlbumPatchData → App.Enum.LicenseType
• App.DTO.BulkAlbumPatchData → App.Enum.OrderSortingType
• App.DTO.BulkAlbumPatchData → App.Enum.PhotoLayoutType
• App.DTO.BulkAlbumPatchData → App.Enum.TimelineAlbumGranularity
• App.DTO.BulkAlbumPatchData → App.Enum.TimelinePhotoGranularity
• App.DTO.CreateSizeVariantFlags → App.Enum.StorageDiskType
• App.DTO.DiagnosticData → App.Enum.MessageType
• App.DTO.ImportEventReport → App.Enum.SeverityType
• App.DTO.ImportParam → App.Enum.UserUploadTrustLevel
• App.DTO.PixelSizeAssignment → App.Enum.PurchasableLicenseType
• App.DTO.PurchasableOption → App.Enum.PurchasableLicenseType
• App.DTO.PurchasableOption → App.Enum.PurchasableSizeVariantType
• App.DTO.PurchasableOptionCreate → App.Enum.PurchasableLicenseType
• App.DTO.PurchasableOptionCreate → App.Enum.PurchasableSizeVariantType
• App.DTO.SortingCriterion → App.Enum.ColumnSortingType
• App.DTO.SortingCriterion → App.Enum.OrderSortingType

Direction

DTO uses Enum, so a change to Enum can break DTO, while a change to DTO can't break Enum.

Position

Below the diagonal: DTO uses a module listed above it, which is the healthy direction.

23→22 DTO uses Actions.Photo✕

Connections

1 pair of types, where a type in DTO uses a type in Actions.Photo.

The types involved

• App.DTO.ImportDTO → App.Actions.Photo.Create

Direction

DTO uses Actions.Photo, so a change to Actions.Photo can break DTO, while a change to DTO can't break Actions.Photo.

Position

Below the diagonal: DTO uses a module listed above it, which is the healthy direction.

23→29 DTO uses Actions.Album part of a loop✕

Connections

1 pair of types, where a type in DTO uses a type in Actions.Album.

The types involved

• App.DTO.ImportDTO → App.Actions.Album.Create

Direction

DTO uses Actions.Album, so a change to Actions.Album can break DTO, while a change to DTO can't break Actions.Album.

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→13 Actions.Diagnostics.Pipes.Checks uses Services✕

Connections

1 pair of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in Services.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.SecurityAdvisoriesCheck → App.Services.SecurityAdvisoriesService

Direction

Actions.Diagnostics.Pipes.Checks uses Services, so a change to Services can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break Services.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

24→14 Actions.Diagnostics.Pipes.Checks uses Repositories✕

Connections

15 pairs of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in Repositories.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.AiVisionFaceRecognitionServiceCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.AiVisionFaceRecognitionServiceConfigCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.AiVisionNsfwServiceCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.BasicPermissionCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.ConfigSanityCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.GDSupportCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.ImageOptCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.ImagickJxlCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.ImagickPdfCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.IniSettingsCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.OldLicenseCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.StatisticsIntegrityCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.SupporterCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.WatermarkerEnabledCheck → App.Repositories.ConfigManager
• App.Actions.Diagnostics.Pipes.Checks.WebshopCheck → App.Repositories.ConfigManager

Direction

Actions.Diagnostics.Pipes.Checks uses Repositories, so a change to Repositories can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break Repositories.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

24→17 Actions.Diagnostics.Pipes.Checks uses Factories✕

Connections

1 pair of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in Factories.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.WebshopCheck → App.Factories.OmnipayFactory

Direction

Actions.Diagnostics.Pipes.Checks uses Factories, so a change to Factories can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break Factories.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

24→19 Actions.Diagnostics.Pipes.Checks uses Services.Image✕

Connections

3 pairs of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in Services.Image.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.AiVisionFaceRecognitionServiceCheck → App.Services.Image.FacialRecognitionService
• App.Actions.Diagnostics.Pipes.Checks.AiVisionFaceRecognitionServiceConfigCheck → App.Services.Image.FacialRecognitionService
• App.Actions.Diagnostics.Pipes.Checks.AiVisionNsfwServiceCheck → App.Services.Image.NsfwDetectionService

Direction

Actions.Diagnostics.Pipes.Checks uses Services.Image, so a change to Services.Image can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break Services.Image.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

24→20 Actions.Diagnostics.Pipes.Checks uses Actions.Shop✕

Connections

1 pair of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in Actions.Shop.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.WebshopCheck → App.Actions.Shop.OrderService

Direction

Actions.Diagnostics.Pipes.Checks uses Actions.Shop, so a change to Actions.Shop can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break Actions.Shop.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

24→23 Actions.Diagnostics.Pipes.Checks uses DTO✕

Connections

1 pair of types, where a type in Actions.Diagnostics.Pipes.Checks uses a type in DTO.

The types involved

• App.Actions.Diagnostics.Pipes.Checks.RecomputeQueueCheck → App.DTO.DiagnosticData

Direction

Actions.Diagnostics.Pipes.Checks uses DTO, so a change to DTO can break Actions.Diagnostics.Pipes.Checks, while a change to Actions.Diagnostics.Pipes.Checks can't break DTO.

Position

Below the diagonal: Actions.Diagnostics.Pipes.Checks uses a module listed above it, which is the healthy direction.

25→11 Actions.User uses Models✕

Connections

5 pairs of types, where a type in Actions.User uses a type in Models.

The types involved

• App.Actions.User.Create → App.Models.User
• App.Actions.User.Notify → App.Models.Photo
• App.Actions.User.ProvisionLdapUser → App.Models.User
• App.Actions.User.Save → App.Models.User
• App.Actions.User.TokenDisable → App.Models.User

Direction

Actions.User uses Models, so a change to Models can break Actions.User, while a change to Actions.User can't break Models.

Position

Below the diagonal: Actions.User uses a module listed above it, which is the healthy direction.

25→14 Actions.User uses Repositories✕

Connections

3 pairs of types, where a type in Actions.User uses a type in Repositories.

The types involved

• App.Actions.User.AssertIdentifierIsUnambiguous → App.Repositories.ConfigManager
• App.Actions.User.Create → App.Repositories.ConfigManager
• App.Actions.User.Save → App.Repositories.ConfigManager

Direction

Actions.User uses Repositories, so a change to Repositories can break Actions.User, while a change to Actions.User can't break Repositories.

Position

Below the diagonal: Actions.User uses a module listed above it, which is the healthy direction.

25→15 Actions.User uses Enum✕

Connections

2 pairs of types, where a type in Actions.User uses a type in Enum.

The types involved

• App.Actions.User.Create → App.Enum.UserUploadTrustLevel
• App.Actions.User.Save → App.Enum.UserUploadTrustLevel

Direction

Actions.User uses Enum, so a change to Enum can break Actions.User, while a change to Actions.User can't break Enum.

Position

Below the diagonal: Actions.User uses a module listed above it, which is the healthy direction.

25→23 Actions.User uses DTO✕

Connections

1 pair of types, where a type in Actions.User uses a type in DTO.

The types involved

• App.Actions.User.ProvisionLdapUser → App.DTO.LdapUser

Direction

Actions.User uses DTO, so a change to DTO can break Actions.User, while a change to Actions.User can't break DTO.

Position

Below the diagonal: Actions.User uses a module listed above it, which is the healthy direction.

26→6 Contracts.Models uses Image.Files✕

Connections

1 pair of types, where a type in Contracts.Models uses a type in Image.Files.

The types involved

• App.Contracts.Models.AbstractSizeVariantNamingStrategy → App.Image.Files.FlysystemFile

Direction

Contracts.Models uses Image.Files, so a change to Image.Files can break Contracts.Models, while a change to Contracts.Models can't break Image.Files.

Position

Below the diagonal: Contracts.Models uses a module listed above it, which is the healthy direction.

26→11 Contracts.Models uses Models✕

Connections

3 pairs of types, where a type in Contracts.Models uses a type in Models.

The types involved

• App.Contracts.Models.AbstractSizeVariantNamingStrategy → App.Models.Photo
• App.Contracts.Models.SizeVariantFactory → App.Models.Photo
• App.Contracts.Models.SizeVariantFactory → App.Models.SizeVariant

Direction

Contracts.Models uses Models, so a change to Models can break Contracts.Models, while a change to Contracts.Models can't break Models.

Position

Below the diagonal: Contracts.Models uses a module listed above it, which is the healthy direction.

26→15 Contracts.Models uses Enum✕

Connections

2 pairs of types, where a type in Contracts.Models uses a type in Enum.

The types involved

• App.Contracts.Models.AbstractSizeVariantNamingStrategy → App.Enum.SizeVariantType
• App.Contracts.Models.SizeVariantFactory → App.Enum.SizeVariantType

Direction

Contracts.Models uses Enum, so a change to Enum can break Contracts.Models, while a change to Contracts.Models can't break Enum.

Position

Below the diagonal: Contracts.Models uses a module listed above it, which is the healthy direction.

26→23 Contracts.Models uses DTO✕

Connections

1 pair of types, where a type in Contracts.Models uses a type in DTO.

The types involved

• App.Contracts.Models.AbstractSizeVariantNamingStrategy → App.DTO.CreateSizeVariantFlags

Direction

Contracts.Models uses DTO, so a change to DTO can break Contracts.Models, while a change to Contracts.Models can't break DTO.

Position

Below the diagonal: Contracts.Models uses a module listed above it, which is the healthy direction.

27→5 Http.Resources.Collections uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Resources.Collections uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Resources.Collections.RootAlbumResource → App.Http.Resources.GalleryConfigs.RootConfig

Direction

Http.Resources.Collections uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Resources.Collections, while a change to Http.Resources.Collections can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Resources.Collections uses a module listed above it, which is the healthy direction.

27→15 Http.Resources.Collections uses Enum✕

Connections

2 pairs of types, where a type in Http.Resources.Collections uses a type in Enum.

The types involved

• App.Http.Resources.Collections.PaginatedAlbumsResource → App.Enum.TimelineAlbumGranularity
• App.Http.Resources.Collections.PaginatedPhotosResource → App.Enum.TimelinePhotoGranularity

Direction

Http.Resources.Collections uses Enum, so a change to Enum can break Http.Resources.Collections, while a change to Http.Resources.Collections can't break Enum.

Position

Below the diagonal: Http.Resources.Collections uses a module listed above it, which is the healthy direction.

27→23 Http.Resources.Collections uses DTO✕

Connections

2 pairs of types, where a type in Http.Resources.Collections uses a type in DTO.

The types involved

• App.Http.Resources.Collections.PaginatedAlbumsResource → App.DTO.AlbumSortingCriterion
• App.Http.Resources.Collections.RootAlbumResource → App.DTO.TopAlbumDTO

Direction

Http.Resources.Collections uses DTO, so a change to DTO can break Http.Resources.Collections, while a change to Http.Resources.Collections can't break DTO.

Position

Below the diagonal: Http.Resources.Collections uses a module listed above it, which is the healthy direction.

28→1 Jobs uses Image✕

Connections

1 pair of types, where a type in Jobs uses a type in Image.

The types involved

• App.Jobs.WatermarkerJob → App.Image.Watermarker

Direction

Jobs uses Image, so a change to Image can break Jobs, while a change to Jobs can't break Image.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→2 Jobs uses Models.Extensions✕

Connections

1 pair of types, where a type in Jobs uses a type in Models.Extensions.

The types involved

• App.Jobs.RecomputeAlbumUserThumbsJob → App.Models.Extensions.Thumb

Direction

Jobs uses Models.Extensions, so a change to Models.Extensions can break Jobs, while a change to Jobs can't break Models.Extensions.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→6 Jobs uses Image.Files✕

Connections

4 pairs of types, where a type in Jobs uses a type in Image.Files.

The types involved

• App.Jobs.EmbedMetadataJob → App.Image.Files.NativeLocalFile
• App.Jobs.ExtractZip → App.Image.Files.ProcessableJobFile
• App.Jobs.ImportImageJob → App.Image.Files.NativeLocalFile
• App.Jobs.ProcessImageJob → App.Image.Files.ProcessableJobFile

Direction

Jobs uses Image.Files, so a change to Image.Files can break Jobs, while a change to Jobs can't break Image.Files.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→11 Jobs uses Models✕

Connections

25 pairs of types, where a type in Jobs uses a type in Models.

The types involved

• App.Jobs.CleanUpExtraction → App.Models.JobHistory
• App.Jobs.EmbedMetadataJob → App.Models.JobHistory
• App.Jobs.EmbedMetadataJob → App.Models.Photo
• App.Jobs.EmbedMetadataJob → App.Models.SizeVariant
• App.Jobs.ExtractColoursJob → App.Models.JobHistory
• App.Jobs.ExtractColoursJob → App.Models.Photo
• App.Jobs.ExtractZip → App.Models.JobHistory
• App.Jobs.GeodecodeLocationJob → App.Models.JobHistory
• App.Jobs.GeodecodeLocationJob → App.Models.Photo
• App.Jobs.ImportImageJob → App.Models.Album
• App.Jobs.ImportImageJob → App.Models.JobHistory
• App.Jobs.ImportImageJob → App.Models.Photo
• App.Jobs.ProcessImageJob → App.Models.JobHistory
• App.Jobs.ProcessImageJob → App.Models.Photo
• App.Jobs.RecomputeAlbumSizeJob → App.Models.Album
• App.Jobs.RecomputeAlbumStatsJob → App.Models.Album
• App.Jobs.RecomputeAlbumStatsJob → App.Models.User
• App.Jobs.RecomputeAlbumUserThumbsJob → App.Models.User
• App.Jobs.UploadSizeVariantToS3Job → App.Models.JobHistory
• App.Jobs.UploadSizeVariantToS3Job → App.Models.SizeVariant
• App.Jobs.UploadTrackToS3Job → App.Models.JobHistory
• App.Jobs.UploadTrackToS3Job → App.Models.Track
• App.Jobs.WatermarkerJob → App.Models.JobHistory
• App.Jobs.WatermarkerJob → App.Models.SizeVariant
• App.Jobs.WebhookDispatchJob → App.Models.Webhook

Direction

Jobs uses Models, so a change to Models can break Jobs, while a change to Jobs can't break Models.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→15 Jobs uses Enum✕

Connections

3 pairs of types, where a type in Jobs uses a type in Enum.

The types involved

• App.Jobs.FileDeleterJob → App.Enum.StorageDiskType
• App.Jobs.ProcessImageJob → App.Enum.UserUploadTrustLevel
• App.Jobs.WebhookDispatchJob → App.Enum.WebhookMethod

Direction

Jobs uses Enum, so a change to Enum can break Jobs, while a change to Jobs can't break Enum.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→17 Jobs uses Factories✕

Connections

2 pairs of types, where a type in Jobs uses a type in Factories.

The types involved

• App.Jobs.ImportImageJob → App.Factories.AlbumFactory
• App.Jobs.ProcessImageJob → App.Factories.AlbumFactory

Direction

Jobs uses Factories, so a change to Factories can break Jobs, while a change to Jobs can't break Factories.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→19 Jobs uses Services.Image✕

Connections

4 pairs of types, where a type in Jobs uses a type in Services.Image.

The types involved

• App.Jobs.DeleteFaceEmbeddingsJob → App.Services.Image.FacialRecognitionService
• App.Jobs.DispatchFaceScanJob → App.Services.Image.FacialRecognitionService
• App.Jobs.DispatchNsfwScanJob → App.Services.Image.NsfwDetectionService
• App.Jobs.ExtractZip → App.Services.Image.FileExtensionService

Direction

Jobs uses Services.Image, so a change to Services.Image can break Jobs, while a change to Jobs can't break Services.Image.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

28→23 Jobs uses DTO✕

Connections

3 pairs of types, where a type in Jobs uses a type in DTO.

The types involved

• App.Jobs.EmbedMetadataJob → App.DTO.MetadataWritePayload
• App.Jobs.ImportImageJob → App.DTO.ImportMode
• App.Jobs.WebhookDispatchJob → App.DTO.WebhookPayload

Direction

Jobs uses DTO, so a change to DTO can break Jobs, while a change to Jobs can't break DTO.

Position

Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.

29→2 Actions.Album uses Models.Extensions✕

Connections

3 pairs of types, where a type in Actions.Album uses a type in Models.Extensions.

The types involved

• App.Actions.Album.SetProtectionPolicy → App.Models.Extensions.BaseAlbum
• App.Actions.Album.Transfer → App.Models.Extensions.BaseAlbum
• App.Actions.Album.Unlock → App.Models.Extensions.BaseAlbum

Direction

Actions.Album uses Models.Extensions, so a change to Models.Extensions can break Actions.Album, while a change to Actions.Album can't break Models.Extensions.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→3 Actions.Album uses Policies✕

Connections

3 pairs of types, where a type in Actions.Album uses a type in Policies.

The types involved

• App.Actions.Album.Breadcrumb → App.Policies.AlbumQueryPolicy
• App.Actions.Album.ListAlbums → App.Policies.AlbumQueryPolicy
• App.Actions.Album.Unlock → App.Policies.AlbumPolicy

Direction

Actions.Album uses Policies, so a change to Policies can break Actions.Album, while a change to Actions.Album can't break Policies.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→5 Actions.Album uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Actions.Album uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Actions.Album.ZipChunkCount → App.Http.Resources.GalleryConfigs.ZipChunkData

Direction

Actions.Album uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Actions.Album, while a change to Actions.Album can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→7 Actions.Album uses SmartAlbums✕

Connections

1 pair of types, where a type in Actions.Album uses a type in SmartAlbums.

The types involved

• App.Actions.Album.SetSmartProtectionPolicy → App.SmartAlbums.BaseSmartAlbum

Direction

Actions.Album uses SmartAlbums, so a change to SmartAlbums can break Actions.Album, while a change to Actions.Album can't break SmartAlbums.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→8 Actions.Album uses Http.Resources.Models.Utils✕

Connections

1 pair of types, where a type in Actions.Album uses a type in Http.Resources.Models.Utils.

The types involved

• App.Actions.Album.SetProtectionPolicy → App.Http.Resources.Models.Utils.AlbumProtectionPolicy

Direction

Actions.Album uses Http.Resources.Models.Utils, so a change to Http.Resources.Models.Utils can break Actions.Album, while a change to Actions.Album can't break Http.Resources.Models.Utils.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→11 Actions.Album uses Models✕

Connections

8 pairs of types, where a type in Actions.Album uses a type in Models.

The types involved

• App.Actions.Album.Breadcrumb → App.Models.Album
• App.Actions.Album.Create → App.Models.Album
• App.Actions.Album.CreatePersonAlbum → App.Models.PersonAlbum
• App.Actions.Album.CreateTagAlbum → App.Models.TagAlbum
• App.Actions.Album.Merge → App.Models.Album
• App.Actions.Album.Move → App.Models.Album
• App.Actions.Album.SetHeader → App.Models.Album
• App.Actions.Album.SetHeader → App.Models.Photo

Direction

Actions.Album uses Models, so a change to Models can break Actions.Album, while a change to Actions.Album can't break Models.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→15 Actions.Album uses Enum✕

Connections

1 pair of types, where a type in Actions.Album uses a type in Enum.

The types involved

• App.Actions.Album.BaseArchive → App.Enum.DownloadVariantType

Direction

Actions.Album uses Enum, so a change to Enum can break Actions.Album, while a change to Actions.Album can't break Enum.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→23 Actions.Album uses DTO✕

Connections

2 pairs of types, where a type in Actions.Album uses a type in DTO.

The types involved

• App.Actions.Album.BaseArchive → App.DTO.ChunkSlice
• App.Actions.Album.BaseArchive → App.DTO.ZippablePhoto

Direction

Actions.Album uses DTO, so a change to DTO can break Actions.Album, while a change to Actions.Album can't break DTO.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→26 Actions.Album uses Contracts.Models✕

Connections

3 pairs of types, where a type in Actions.Album uses a type in Contracts.Models.

The types involved

• App.Actions.Album.BaseArchive → App.Contracts.Models.AbstractAlbum
• App.Actions.Album.PositionData → App.Contracts.Models.AbstractAlbum
• App.Actions.Album.ZipChunkCount → App.Contracts.Models.AbstractAlbum

Direction

Actions.Album uses Contracts.Models, so a change to Contracts.Models can break Actions.Album, while a change to Actions.Album can't break Contracts.Models.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

29→27 Actions.Album uses Http.Resources.Collections✕

Connections

1 pair of types, where a type in Actions.Album uses a type in Http.Resources.Collections.

The types involved

• App.Actions.Album.PositionData → App.Http.Resources.Collections.PositionDataResource

Direction

Actions.Album uses Http.Resources.Collections, so a change to Http.Resources.Collections can break Actions.Album, while a change to Actions.Album can't break Http.Resources.Collections.

Position

Below the diagonal: Actions.Album uses a module listed above it, which is the healthy direction.

30→3 Actions.Albums uses Policies✕

Connections

3 pairs of types, where a type in Actions.Albums uses a type in Policies.

The types involved

• App.Actions.Albums.Flow → App.Policies.AlbumQueryPolicy
• App.Actions.Albums.PositionData → App.Policies.PhotoQueryPolicy
• App.Actions.Albums.Top → App.Policies.AlbumQueryPolicy

Direction

Actions.Albums uses Policies, so a change to Policies can break Actions.Albums, while a change to Actions.Albums can't break Policies.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→4 Actions.Albums uses Services.Cache✕

Connections

2 pairs of types, where a type in Actions.Albums uses a type in Services.Cache.

The types involved

• App.Actions.Albums.Top → App.Services.Cache.CacheKeyProvider
• App.Actions.Albums.Top → App.Services.Cache.ManagedCacheService

Direction

Actions.Albums uses Services.Cache, so a change to Services.Cache can break Actions.Albums, while a change to Actions.Albums can't break Services.Cache.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→11 Actions.Albums uses Models✕

Connections

1 pair of types, where a type in Actions.Albums uses a type in Models.

The types involved

• App.Actions.Albums.Top → App.Models.User

Direction

Actions.Albums uses Models, so a change to Models can break Actions.Albums, while a change to Actions.Albums can't break Models.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→14 Actions.Albums uses Repositories✕

Connections

3 pairs of types, where a type in Actions.Albums uses a type in Repositories.

The types involved

• App.Actions.Albums.Flow → App.Repositories.ConfigManager
• App.Actions.Albums.PositionData → App.Repositories.ConfigManager
• App.Actions.Albums.Top → App.Repositories.ConfigManager

Direction

Actions.Albums uses Repositories, so a change to Repositories can break Actions.Albums, while a change to Actions.Albums can't break Repositories.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→15 Actions.Albums uses Enum✕

Connections

2 pairs of types, where a type in Actions.Albums uses a type in Enum.

The types involved

• App.Actions.Albums.Top → App.Enum.ColumnSortingType
• App.Actions.Albums.Top → App.Enum.OrderSortingType

Direction

Actions.Albums uses Enum, so a change to Enum can break Actions.Albums, while a change to Actions.Albums can't break Enum.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→17 Actions.Albums uses Factories✕

Connections

2 pairs of types, where a type in Actions.Albums uses a type in Factories.

The types involved

• App.Actions.Albums.Flow → App.Factories.AlbumFactory
• App.Actions.Albums.Top → App.Factories.AlbumFactory

Direction

Actions.Albums uses Factories, so a change to Factories can break Actions.Albums, while a change to Actions.Albums can't break Factories.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→23 Actions.Albums uses DTO✕

Connections

2 pairs of types, where a type in Actions.Albums uses a type in DTO.

The types involved

• App.Actions.Albums.Top → App.DTO.AlbumSortingCriterion
• App.Actions.Albums.Top → App.DTO.TopAlbumDTO

Direction

Actions.Albums uses DTO, so a change to DTO can break Actions.Albums, while a change to Actions.Albums can't break DTO.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

30→27 Actions.Albums uses Http.Resources.Collections✕

Connections

1 pair of types, where a type in Actions.Albums uses a type in Http.Resources.Collections.

The types involved

• App.Actions.Albums.PositionData → App.Http.Resources.Collections.PositionDataResource

Direction

Actions.Albums uses Http.Resources.Collections, so a change to Http.Resources.Collections can break Actions.Albums, while a change to Actions.Albums can't break Http.Resources.Collections.

Position

Below the diagonal: Actions.Albums uses a module listed above it, which is the healthy direction.

31→3 Actions.Photo.StructOfArrays uses Policies✕

Connections

1 pair of types, where a type in Actions.Photo.StructOfArrays uses a type in Policies.

The types involved

• App.Actions.Photo.StructOfArrays.ResolvesPhotoGrants → App.Policies.AlbumQueryPolicy

Direction

Actions.Photo.StructOfArrays uses Policies, so a change to Policies can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Policies.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→9 Actions.Photo.StructOfArrays uses Http.Resources.V3✕

Connections

3 pairs of types, where a type in Actions.Photo.StructOfArrays uses a type in Http.Resources.V3.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoBuckets → App.Http.Resources.V3.PhotoBucketResource
• App.Actions.Photo.StructOfArrays.QueryPhotoDetails → App.Http.Resources.V3.PhotoDetailResource
• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Http.Resources.V3.PhotoRatioResource

Direction

Actions.Photo.StructOfArrays uses Http.Resources.V3, so a change to Http.Resources.V3 can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Http.Resources.V3.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→11 Actions.Photo.StructOfArrays uses Models✕

Connections

6 pairs of types, where a type in Actions.Photo.StructOfArrays uses a type in Models.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoBuckets → App.Models.Album
• App.Actions.Photo.StructOfArrays.QueryPhotoBuckets → App.Models.User
• App.Actions.Photo.StructOfArrays.QueryPhotoDetails → App.Models.User
• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Models.User
• App.Actions.Photo.StructOfArrays.ResolvesPhotoGrants → App.Models.User
• App.Actions.Photo.StructOfArrays.ResolvesPhotoSource → App.Models.User

Direction

Actions.Photo.StructOfArrays uses Models, so a change to Models can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Models.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→13 Actions.Photo.StructOfArrays uses Services✕

Connections

2 pairs of types, where a type in Actions.Photo.StructOfArrays uses a type in Services.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Services.BucketScheme
• App.Actions.Photo.StructOfArrays.ResolvesPhotoSource → App.Services.BucketScheme

Direction

Actions.Photo.StructOfArrays uses Services, so a change to Services can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Services.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→14 Actions.Photo.StructOfArrays uses Repositories✕

Connections

2 pairs of types, where a type in Actions.Photo.StructOfArrays uses a type in Repositories.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoDetails → App.Repositories.ConfigManager
• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Repositories.ConfigManager

Direction

Actions.Photo.StructOfArrays uses Repositories, so a change to Repositories can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Repositories.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→15 Actions.Photo.StructOfArrays uses Enum✕

Connections

1 pair of types, where a type in Actions.Photo.StructOfArrays uses a type in Enum.

The types involved

• App.Actions.Photo.StructOfArrays.ResolvesPhotoSource → App.Enum.TimelinePhotoGranularity

Direction

Actions.Photo.StructOfArrays uses Enum, so a change to Enum can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Enum.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→19 Actions.Photo.StructOfArrays uses Services.Image✕

Connections

1 pair of types, where a type in Actions.Photo.StructOfArrays uses a type in Services.Image.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Services.Image.FileExtensionService

Direction

Actions.Photo.StructOfArrays uses Services.Image, so a change to Services.Image can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Services.Image.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→23 Actions.Photo.StructOfArrays uses DTO✕

Connections

1 pair of types, where a type in Actions.Photo.StructOfArrays uses a type in DTO.

The types involved

• App.Actions.Photo.StructOfArrays.ResolvesPhotoSource → App.DTO.PhotoSortingCriterion

Direction

Actions.Photo.StructOfArrays uses DTO, so a change to DTO can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break DTO.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

31→26 Actions.Photo.StructOfArrays uses Contracts.Models✕

Connections

4 pairs of types, where a type in Actions.Photo.StructOfArrays uses a type in Contracts.Models.

The types involved

• App.Actions.Photo.StructOfArrays.QueryPhotoBuckets → App.Contracts.Models.AbstractAlbum
• App.Actions.Photo.StructOfArrays.QueryPhotoDetails → App.Contracts.Models.AbstractAlbum
• App.Actions.Photo.StructOfArrays.QueryPhotoRatios → App.Contracts.Models.AbstractAlbum
• App.Actions.Photo.StructOfArrays.ResolvesPhotoSource → App.Contracts.Models.AbstractAlbum

Direction

Actions.Photo.StructOfArrays uses Contracts.Models, so a change to Contracts.Models can break Actions.Photo.StructOfArrays, while a change to Actions.Photo.StructOfArrays can't break Contracts.Models.

Position

Below the diagonal: Actions.Photo.StructOfArrays uses a module listed above it, which is the healthy direction.

32→2 Contracts.Http.Requests uses Models.Extensions✕

Connections

1 pair of types, where a type in Contracts.Http.Requests uses a type in Models.Extensions.

The types involved

• App.Contracts.Http.Requests.HasBaseAlbum → App.Models.Extensions.BaseAlbum

Direction

Contracts.Http.Requests uses Models.Extensions, so a change to Models.Extensions can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break Models.Extensions.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

32→10 Contracts.Http.Requests uses Http.Resources.Models✕

Connections

1 pair of types, where a type in Contracts.Http.Requests uses a type in Http.Resources.Models.

The types involved

• App.Contracts.Http.Requests.HasAccessPermissionResource → App.Http.Resources.Models.AccessPermissionResource

Direction

Contracts.Http.Requests uses Http.Resources.Models, so a change to Http.Resources.Models can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break Http.Resources.Models.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

32→11 Contracts.Http.Requests uses Models✕

Connections

12 pairs of types, where a type in Contracts.Http.Requests uses a type in Models.

The types involved

• App.Contracts.Http.Requests.HasAccessPermission → App.Models.AccessPermission
• App.Contracts.Http.Requests.HasAlbum → App.Models.Album
• App.Contracts.Http.Requests.HasBasket → App.Models.Order
• App.Contracts.Http.Requests.HasFace → App.Models.Face
• App.Contracts.Http.Requests.HasParentAlbum → App.Models.Album
• App.Contracts.Http.Requests.HasPerson → App.Models.Person
• App.Contracts.Http.Requests.HasPersonAlbum → App.Models.PersonAlbum
• App.Contracts.Http.Requests.HasPhoto → App.Models.Photo
• App.Contracts.Http.Requests.HasTag → App.Models.Tag
• App.Contracts.Http.Requests.HasTagAlbum → App.Models.TagAlbum
• App.Contracts.Http.Requests.HasUser → App.Models.User
• App.Contracts.Http.Requests.HasUserGroup → App.Models.UserGroup

Direction

Contracts.Http.Requests uses Models, so a change to Models can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break Models.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

32→15 Contracts.Http.Requests uses Enum✕

Connections

8 pairs of types, where a type in Contracts.Http.Requests uses a type in Enum.

The types involved

• App.Contracts.Http.Requests.HasLicense → App.Enum.LicenseType
• App.Contracts.Http.Requests.HasPhotoLayout → App.Enum.PhotoLayoutType
• App.Contracts.Http.Requests.HasRole → App.Enum.UserGroupRole
• App.Contracts.Http.Requests.HasSizeVariant → App.Enum.DownloadVariantType
• App.Contracts.Http.Requests.HasTimelineAlbum → App.Enum.TimelineAlbumGranularity
• App.Contracts.Http.Requests.HasTimelinePhoto → App.Enum.TimelinePhotoGranularity
• App.Contracts.Http.Requests.HasTitleCustomization → App.Enum.AlbumTitleColor
• App.Contracts.Http.Requests.HasTitleCustomization → App.Enum.AlbumTitlePosition

Direction

Contracts.Http.Requests uses Enum, so a change to Enum can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break Enum.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

32→23 Contracts.Http.Requests uses DTO✕

Connections

2 pairs of types, where a type in Contracts.Http.Requests uses a type in DTO.

The types involved

• App.Contracts.Http.Requests.HasAlbumSortingCriterion → App.DTO.AlbumSortingCriterion
• App.Contracts.Http.Requests.HasPhotoSortingCriterion → App.DTO.PhotoSortingCriterion

Direction

Contracts.Http.Requests uses DTO, so a change to DTO can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break DTO.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

32→26 Contracts.Http.Requests uses Contracts.Models✕

Connections

2 pairs of types, where a type in Contracts.Http.Requests uses a type in Contracts.Models.

The types involved

• App.Contracts.Http.Requests.HasAbstractAlbum → App.Contracts.Models.AbstractAlbum
• App.Contracts.Http.Requests.HasFromAlbum → App.Contracts.Models.AbstractAlbum

Direction

Contracts.Http.Requests uses Contracts.Models, so a change to Contracts.Models can break Contracts.Http.Requests, while a change to Contracts.Http.Requests can't break Contracts.Models.

Position

Below the diagonal: Contracts.Http.Requests uses a module listed above it, which is the healthy direction.

33→5 Http.Controllers uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Controllers uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Controllers.LandingPageController → App.Http.Resources.GalleryConfigs.LandingPageResource

Direction

Http.Controllers uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Controllers, while a change to Http.Controllers can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

33→8 Http.Controllers uses Http.Resources.Models.Utils✕

Connections

1 pair of types, where a type in Http.Controllers uses a type in Http.Resources.Models.Utils.

The types involved

• App.Http.Controllers.ProfileController → App.Http.Resources.Models.Utils.UserToken

Direction

Http.Controllers uses Http.Resources.Models.Utils, so a change to Http.Resources.Models.Utils can break Http.Controllers, while a change to Http.Controllers can't break Http.Resources.Models.Utils.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

33→10 Http.Controllers uses Http.Resources.Models✕

Connections

3 pairs of types, where a type in Http.Controllers uses a type in Http.Resources.Models.

The types involved

• App.Http.Controllers.AuthController → App.Http.Resources.Models.UserResource
• App.Http.Controllers.ProfileController → App.Http.Resources.Models.UserResource
• App.Http.Controllers.RenamerController → App.Http.Resources.Models.RenamerRuleResource

Direction

Http.Controllers uses Http.Resources.Models, so a change to Http.Resources.Models can break Http.Controllers, while a change to Http.Controllers can't break Http.Resources.Models.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

33→13 Http.Controllers uses Services✕

Connections

2 pairs of types, where a type in Http.Controllers uses a type in Services.

The types involved

• App.Http.Controllers.RSSController → App.Services.GalleryLockState
• App.Http.Controllers.VueController → App.Services.GalleryLockState

Direction

Http.Controllers uses Services, so a change to Services can break Http.Controllers, while a change to Http.Controllers can't break Services.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

33→25 Http.Controllers uses Actions.User✕

Connections

3 pairs of types, where a type in Http.Controllers uses a type in Actions.User.

The types involved

• App.Http.Controllers.ProfileController → App.Actions.User.Create
• App.Http.Controllers.ProfileController → App.Actions.User.TokenDisable
• App.Http.Controllers.ProfileController → App.Actions.User.TokenReset

Direction

Http.Controllers uses Actions.User, so a change to Actions.User can break Http.Controllers, while a change to Http.Controllers can't break Actions.User.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

33→26 Http.Controllers uses Contracts.Models✕

Connections

1 pair of types, where a type in Http.Controllers uses a type in Contracts.Models.

The types involved

• App.Http.Controllers.VueController → App.Contracts.Models.AbstractAlbum

Direction

Http.Controllers uses Contracts.Models, so a change to Contracts.Models can break Http.Controllers, while a change to Http.Controllers can't break Contracts.Models.

Position

Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.

34→3 Http.Controllers.Admin uses Policies✕

Connections

1 pair of types, where a type in Http.Controllers.Admin uses a type in Policies.

The types involved

• App.Http.Controllers.Admin.DiagnosticsController → App.Policies.AlbumQueryPolicy

Direction

Http.Controllers.Admin uses Policies, so a change to Policies can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Policies.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→5 Http.Controllers.Admin uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Controllers.Admin uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Controllers.Admin.SettingsController → App.Http.Resources.GalleryConfigs.SettingsConfig

Direction

Http.Controllers.Admin uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→10 Http.Controllers.Admin uses Http.Resources.Models✕

Connections

9 pairs of types, where a type in Http.Controllers.Admin uses a type in Http.Resources.Models.

The types involved

• App.Http.Controllers.Admin.AdminDashboardController → App.Http.Resources.Models.AdminStatsResource
• App.Http.Controllers.Admin.AdminUpdateStatusController → App.Http.Resources.Models.AdminUpdateStatusResource
• App.Http.Controllers.Admin.LandingFeaturedItemController → App.Http.Resources.Models.LandingFeaturedItemResource
• App.Http.Controllers.Admin.LandingLinkController → App.Http.Resources.Models.LandingLinkResource
• App.Http.Controllers.Admin.ModerationController → App.Http.Resources.Models.PhotoResource
• App.Http.Controllers.Admin.UserGroupsController → App.Http.Resources.Models.UserGroupResource
• App.Http.Controllers.Admin.UserGroupsManagementController → App.Http.Resources.Models.UserGroupResource
• App.Http.Controllers.Admin.UserManagementController → App.Http.Resources.Models.UserManagementResource
• App.Http.Controllers.Admin.WebhookController → App.Http.Resources.Models.WebhookResource

Direction

Http.Controllers.Admin uses Http.Resources.Models, so a change to Http.Resources.Models can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Http.Resources.Models.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→11 Http.Controllers.Admin uses Models✕

Connections

1 pair of types, where a type in Http.Controllers.Admin uses a type in Models.

The types involved

• App.Http.Controllers.Admin.BulkAlbumController → App.Models.Album

Direction

Http.Controllers.Admin uses Models, so a change to Models can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Models.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→13 Http.Controllers.Admin uses Services✕

Connections

3 pairs of types, where a type in Http.Controllers.Admin uses a type in Services.

The types involved

• App.Http.Controllers.Admin.AdminDashboardController → App.Services.AdminStatsService
• App.Http.Controllers.Admin.ModerationController → App.Services.ModerationHistory
• App.Http.Controllers.Admin.SecurityAdvisoriesController → App.Services.SecurityAdvisoriesService

Direction

Http.Controllers.Admin uses Services, so a change to Services can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Services.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→14 Http.Controllers.Admin uses Repositories✕

Connections

1 pair of types, where a type in Http.Controllers.Admin uses a type in Repositories.

The types involved

• App.Http.Controllers.Admin.ModerationController → App.Repositories.ConfigManager

Direction

Http.Controllers.Admin uses Repositories, so a change to Repositories can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Repositories.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→20 Http.Controllers.Admin uses Actions.Shop✕

Connections

1 pair of types, where a type in Http.Controllers.Admin uses a type in Actions.Shop.

The types involved

• App.Http.Controllers.Admin.ShopManagementController → App.Actions.Shop.PurchasableService

Direction

Http.Controllers.Admin uses Actions.Shop, so a change to Actions.Shop can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Actions.Shop.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→25 Http.Controllers.Admin uses Actions.User✕

Connections

2 pairs of types, where a type in Http.Controllers.Admin uses a type in Actions.User.

The types involved

• App.Http.Controllers.Admin.UserManagementController → App.Actions.User.Create
• App.Http.Controllers.Admin.UserManagementController → App.Actions.User.Save

Direction

Http.Controllers.Admin uses Actions.User, so a change to Actions.User can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Actions.User.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

34→27 Http.Controllers.Admin uses Http.Resources.Collections✕

Connections

6 pairs of types, where a type in Http.Controllers.Admin uses a type in Http.Resources.Collections.

The types involved

• App.Http.Controllers.Admin.LandingFeaturedItemController → App.Http.Resources.Collections.LandingFeaturedItemCollection
• App.Http.Controllers.Admin.LandingLinkController → App.Http.Resources.Collections.LandingLinkCollection
• App.Http.Controllers.Admin.ModerationController → App.Http.Resources.Collections.PaginatedModerationHistoryResource
• App.Http.Controllers.Admin.ModerationController → App.Http.Resources.Collections.PaginatedModerationResource
• App.Http.Controllers.Admin.UserGroupsController → App.Http.Resources.Collections.UserGroupDataResource
• App.Http.Controllers.Admin.WebhookController → App.Http.Resources.Collections.PaginatedWebhookResource

Direction

Http.Controllers.Admin uses Http.Resources.Collections, so a change to Http.Resources.Collections can break Http.Controllers.Admin, while a change to Http.Controllers.Admin can't break Http.Resources.Collections.

Position

Below the diagonal: Http.Controllers.Admin uses a module listed above it, which is the healthy direction.

35→1 Http.Controllers.Admin.Maintenance uses Image✕

Connections

2 pairs of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Image.

The types involved

• App.Http.Controllers.Admin.Maintenance.GenSizeVariants → App.Image.PlaceholderEncoder
• App.Http.Controllers.Admin.Maintenance.GenSizeVariants → App.Image.SizeVariantDimensionHelpers

Direction

Http.Controllers.Admin.Maintenance uses Image, so a change to Image can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Image.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→5 Http.Controllers.Admin.Maintenance uses Http.Resources.GalleryConfigs✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Http.Resources.GalleryConfigs.

The types involved

• App.Http.Controllers.Admin.Maintenance.RegisterController → App.Http.Resources.GalleryConfigs.RegisterData

Direction

Http.Controllers.Admin.Maintenance uses Http.Resources.GalleryConfigs, so a change to Http.Resources.GalleryConfigs can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Http.Resources.GalleryConfigs.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→18 Http.Controllers.Admin.Maintenance uses Listeners✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Listeners.

The types involved

• App.Http.Controllers.Admin.Maintenance.FulfillOrders → App.Listeners.OrderCompletedListener

Direction

Http.Controllers.Admin.Maintenance uses Listeners, so a change to Listeners can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Listeners.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→19 Http.Controllers.Admin.Maintenance uses Services.Image✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Services.Image.

The types involved

• App.Http.Controllers.Admin.Maintenance.BulkScanFaces → App.Services.Image.FaceDetectionService

Direction

Http.Controllers.Admin.Maintenance uses Services.Image, so a change to Services.Image can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Services.Image.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→20 Http.Controllers.Admin.Maintenance uses Actions.Shop✕

Connections

2 pairs of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Actions.Shop.

The types involved

• App.Http.Controllers.Admin.Maintenance.FlushOldOrders → App.Actions.Shop.OrderService
• App.Http.Controllers.Admin.Maintenance.FulfillOrders → App.Actions.Shop.OrderService

Direction

Http.Controllers.Admin.Maintenance uses Actions.Shop, so a change to Actions.Shop can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Actions.Shop.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→22 Http.Controllers.Admin.Maintenance uses Actions.Photo✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Actions.Photo.

The types involved

• App.Http.Controllers.Admin.Maintenance.DuplicateFinder → App.Actions.Photo.DuplicateFinder

Direction

Http.Controllers.Admin.Maintenance uses Actions.Photo, so a change to Actions.Photo can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Actions.Photo.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→24 Http.Controllers.Admin.Maintenance uses Actions.Diagnostics.Pipes.Checks✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Actions.Diagnostics.Pipes.Checks.

The types involved

• App.Http.Controllers.Admin.Maintenance.StatisticsCheck → App.Actions.Diagnostics.Pipes.Checks.StatisticsIntegrityCheck

Direction

Http.Controllers.Admin.Maintenance uses Actions.Diagnostics.Pipes.Checks, so a change to Actions.Diagnostics.Pipes.Checks can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Actions.Diagnostics.Pipes.Checks.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

35→26 Http.Controllers.Admin.Maintenance uses Contracts.Models✕

Connections

1 pair of types, where a type in Http.Controllers.Admin.Maintenance uses a type in Contracts.Models.

The types involved

• App.Http.Controllers.Admin.Maintenance.GenSizeVariants → App.Contracts.Models.SizeVariantFactory

Direction

Http.Controllers.Admin.Maintenance uses Contracts.Models, so a change to Contracts.Models can break Http.Controllers.Admin.Maintenance, while a change to Http.Controllers.Admin.Maintenance can't break Contracts.Models.

Position

Below the diagonal: Http.Controllers.Admin.Maintenance uses a module listed above it, which is the healthy direction.

36→1 Http.Controllers.AiVision uses Image✕

Connections

1 pair of types, where a type in Http.Controllers.AiVision uses a type in Image.

The types involved

• App.Http.Controllers.AiVision.FacePhotoAssetController → App.Image.Watermarker

Direction

Http.Controllers.AiVision uses Image, so a change to Image can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Image.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→3 Http.Controllers.AiVision uses Policies✕

Connections

1 pair of types, where a type in Http.Controllers.AiVision uses a type in Policies.

The types involved

• App.Http.Controllers.AiVision.FaceClusterController → App.Policies.PhotoQueryPolicy

Direction

Http.Controllers.AiVision uses Policies, so a change to Policies can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Policies.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→9 Http.Controllers.AiVision uses Http.Resources.V3✕

Connections

2 pairs of types, where a type in Http.Controllers.AiVision uses a type in Http.Resources.V3.

The types involved

• App.Http.Controllers.AiVision.FaceQueueController → App.Http.Resources.V3.FaceQueueResource
• App.Http.Controllers.AiVision.PeopleListController → App.Http.Resources.V3.PeopleListResource

Direction

Http.Controllers.AiVision uses Http.Resources.V3, so a change to Http.Resources.V3 can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Http.Resources.V3.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→10 Http.Controllers.AiVision uses Http.Resources.Models✕

Connections

6 pairs of types, where a type in Http.Controllers.AiVision uses a type in Http.Resources.Models.

The types involved

• App.Http.Controllers.AiVision.FaceController → App.Http.Resources.Models.FaceResource
• App.Http.Controllers.AiVision.PeopleController → App.Http.Resources.Models.PersonResource
• App.Http.Controllers.AiVision.PersonClaimController → App.Http.Resources.Models.PersonResource
• App.Http.Controllers.AiVision.PhotoFacesController → App.Http.Resources.Models.PhotoFacesResource
• App.Http.Controllers.AiVision.PhotoNsfwDetectionsController → App.Http.Resources.Models.PhotoNsfwDetectionsResource
• App.Http.Controllers.AiVision.SelfieClaimController → App.Http.Resources.Models.PersonResource

Direction

Http.Controllers.AiVision uses Http.Resources.Models, so a change to Http.Resources.Models can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Http.Resources.Models.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→14 Http.Controllers.AiVision uses Repositories✕

Connections

1 pair of types, where a type in Http.Controllers.AiVision uses a type in Repositories.

The types involved

• App.Http.Controllers.AiVision.SelfieClaimController → App.Repositories.ConfigManager

Direction

Http.Controllers.AiVision uses Repositories, so a change to Repositories can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Repositories.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→17 Http.Controllers.AiVision uses Factories✕

Connections

3 pairs of types, where a type in Http.Controllers.AiVision uses a type in Factories.

The types involved

• App.Http.Controllers.AiVision.FaceClusterController → App.Factories.PersonFactory
• App.Http.Controllers.AiVision.FaceController → App.Factories.PersonFactory
• App.Http.Controllers.AiVision.FaceMaintenanceController → App.Factories.PersonFactory

Direction

Http.Controllers.AiVision uses Factories, so a change to Factories can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Factories.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→19 Http.Controllers.AiVision uses Services.Image✕

Connections

5 pairs of types, where a type in Http.Controllers.AiVision uses a type in Services.Image.

The types involved

• App.Http.Controllers.AiVision.FaceDetectionController → App.Services.Image.FaceDetectionService
• App.Http.Controllers.AiVision.NsfwConfigController → App.Services.Image.NsfwDetectionService
• App.Http.Controllers.AiVision.NsfwDetectionController → App.Services.Image.NsfwActionService
• App.Http.Controllers.AiVision.NsfwDetectionController → App.Services.Image.NsfwDetectionService
• App.Http.Controllers.AiVision.SelfieClaimController → App.Services.Image.FacialRecognitionService

Direction

Http.Controllers.AiVision uses Services.Image, so a change to Services.Image can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Services.Image.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.

36→27 Http.Controllers.AiVision uses Http.Resources.Collections✕

Connections

7 pairs of types, where a type in Http.Controllers.AiVision uses a type in Http.Resources.Collections.

The types involved

• App.Http.Controllers.AiVision.AlbumPeopleController → App.Http.Resources.Collections.PaginatedPersonsResource
• App.Http.Controllers.AiVision.FaceClusterController → App.Http.Resources.Collections.PaginatedClustersResource
• App.Http.Controllers.AiVision.FaceClusterController → App.Http.Resources.Collections.PaginatedFaceResource
• App.Http.Controllers.AiVision.FaceMaintenanceController → App.Http.Resources.Collections.PaginatedFaceResource
• App.Http.Controllers.AiVision.NsfwFindingsController → App.Http.Resources.Collections.PaginatedNsfwFindingsResource
• App.Http.Controllers.AiVision.PeopleController → App.Http.Resources.Collections.PaginatedPersonsResource
• App.Http.Controllers.AiVision.PersonPhotosController → App.Http.Resources.Collections.PaginatedPhotosResource

Direction

Http.Controllers.AiVision uses Http.Resources.Collections, so a change to Http.Resources.Collections can break Http.Controllers.AiVision, while a change to Http.Controllers.AiVision can't break Http.Resources.Collections.

Position

Below the diagonal: Http.Controllers.AiVision uses a module listed above it, which is the healthy direction.