Executive summary
SapiensAnatis/Dawnshard has a provisional result, because the code didn't build. Its score is held back in part because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 47.5 out of 100, and the ratings may change once the code builds. 81 of its 95 critical findings are security problems.
Security and Compliance, at 36.6, is the weakest lens and counts most in the score. The best first step for the work it takes is moving to stable dependency versions, worth about 5.2 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 7.4 points. Raising Security and Compliance to 70 would lift the score to about 56.4.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifteen secrets can leak from the build pipeline, and twelve known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Passing outside input through environment variables would fix the eight pipeline steps that put outside input straight into a shell command, and the seven passwords or keys in the code's history need replacing, with the old ones switched off. The seven data fields that are written but never read need removing.
The product code is 91,103 lines, about €190,000 to rebuild.
If Security and Compliance rose from 36.6 to 70, the lowest score rated Strong, the score would rise from 47.5 to about 56.4.
Rebuild cost: about €190,000 · Estimate
| Cost to rebuild | €64,000 to €320,000, for 1,075 to 3,411 hours of work, about 1.3 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 91,103 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Infrastructure.Results | 2 Shared.Definitions.Enums | 3 Shared.PlayerDetails | 4 Database.Entities | 5 Features.Shared.Options | 6 Infrastructure | 7 Shared.MasterAsset.Models | 8 Database | 9 Models.Generated | 10 Database.Repositories | 11 Features.Present | 12 Features.CoOp | 13 Features.Friends | 14 Features.Player | 15 Features.Shared.Reward.Handlers | 16 Features.Shared.Reward | 17 Features.Quest | 18 Features.Shop | 19 Features.Chara | 20 Features.Trade | 21 Features.Dungeon.Record | 22 Features.Event | 23 Features.Dungeon | 24 Features.Wall | 25 Features.Tutorial | 26 Features.Story | 27 Features.Summoning | 28 Features.Login.Actions | 29 Features.Dmode | 30 Features.Shared | 31 Features.Dragons | 32 Features.Fort | 33 Features.Dungeon.Start | 34 Features.Parties | 35 Features.Missions.InitialProgress | 36 Features.Missions | 37 Features.AbilityCrests | 38 Features.Login | 39 Features.Login.SavefileUpdate | 40 Features.Login.Savefile |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Infrastructure.Results | ||||||||||||||||||||||||||||||||||||||||
| 2 Shared.Definitions.Enums | ||||||||||||||||||||||||||||||||||||||||
| 3 Shared.PlayerDetails | ||||||||||||||||||||||||||||||||||||||||
| 4 Database.Entities | 36 | |||||||||||||||||||||||||||||||||||||||
| 5 Features.Shared.Options | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Infrastructure | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 Shared.MasterAsset.Models | 57 | |||||||||||||||||||||||||||||||||||||||
| 8 Database | 2 | 64 | ||||||||||||||||||||||||||||||||||||||
| 9 Models.Generated | 11 | 3 | 9 | 9 | ||||||||||||||||||||||||||||||||||||
| 10 Database.Repositories | 15 | 6 | 33 | 2 | 7 | |||||||||||||||||||||||||||||||||||
| 11 Features.Present | 1 | 1 | 1 | 6 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 12 Features.CoOp | 1 | 2 | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 13 Features.Friends | 1 | 1 | 5 | 4 | 1 | 4 | 2 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 14 Features.Player | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Features.Shared.Reward.Handlers | 18 | 5 | 6 | 9 | 3 | 1 | 21 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 16 Features.Shared.Reward | 5 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 17 Features.Quest | 1 | 2 | 2 | 1 | 2 | 1 | 2 | 2 | 1 | 2 | 3 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||
| 18 Features.Shop | 1 | 9 | 1 | 4 | 1 | 1 | 2 | 3 | 1 | 5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 19 Features.Chara | 1 | 4 | 3 | 1 | 1 | 1 | 3 | 2 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 20 Features.Trade | 3 | 5 | 1 | 2 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||
| 21 Features.Dungeon.Record | 1 | 1 | 1 | 2 | 11 | 1 | 1 | 1 | 2 | 1 | 3 | 1 | 1 | 9 | 1 | 1 | 1 | |||||||||||||||||||||||
| 22 Features.Event | 6 | 2 | 10 | 1 | 6 | 1 | 2 | 3 | 1 | 7 | 4 | 6 | 2 | |||||||||||||||||||||||||||
| 23 Features.Dungeon | 1 | 5 | 2 | 12 | 1 | 2 | 4 | 1 | 15 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||
| 24 Features.Wall | 3 | 2 | 1 | 4 | 3 | 1 | 2 | 4 | 1 | 4 | 3 | 2 | ||||||||||||||||||||||||||||
| 25 Features.Tutorial | 1 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 Features.Story | 2 | 4 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||
| 27 Features.Summoning | 2 | 8 | 1 | 1 | 2 | 5 | 3 | 2 | 3 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 28 Features.Login.Actions | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 29 Features.Dmode | 1 | 7 | 1 | 10 | 2 | 1 | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 30 Features.Shared | 1 | 1 | 4 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 31 Features.Dragons | 1 | 4 | 3 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 32 Features.Fort | 1 | 8 | 3 | 6 | 1 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||
| 33 Features.Dungeon.Start | 2 | 1 | 1 | 1 | 2 | 1 | 4 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 6 | 1 | 1 | 1 | ||||||||||||||||||||||
| 34 Features.Parties | 1 | 6 | 1 | 12 | 1 | 5 | 2 | 3 | 4 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 35 Features.Missions.InitialProgress | 10 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 36 Features.Missions | 1 | 28 | 1 | 6 | 1 | 1 | 1 | 9 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 37 Features.AbilityCrests | 3 | 9 | 1 | 5 | 1 | 3 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 38 Features.Login | 3 | 1 | 3 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 4 | 1 | 1 | |||||||||||||||||||||||||||
| 39 Features.Login.SavefileUpdate | 2 | 10 | 14 | 6 | 3 | 1 | 1 | 2 | 3 | 2 | 7 | 5 | 2 | 1 | 4 | |||||||||||||||||||||||||
| 40 Features.Login.Savefile | 2 | 5 | 3 | 12 | 1 | 1 | 2 | 12 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
4→2 Database.Entities uses Shared.Definitions.Enums✕
- Connections
- 36 pairs of types, where a type in Database.Entities uses a type in Shared.Definitions.Enums. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DragaliaAPI.Database.Entities.DbAbilityCrest→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Database.Entities.DbAbilityCrestSet→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Database.Entities.DbEmblem→DragaliaAPI.Shared.Definitions.Enums.EmblemsDragaliaAPI.Database.Entities.DbFortBuild→DragaliaAPI.Shared.Definitions.Enums.FortBuildStatusDragaliaAPI.Database.Entities.DbFortBuild→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Database.Entities.DbPlayerCharaData→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerCharaHonor→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerDmodeChara→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerDmodeDungeon→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerDmodeDungeon→DragaliaAPI.Shared.Definitions.Enums.DungeonStateDragaliaAPI.Database.Entities.DbPlayerDmodeExpedition→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerDmodeExpedition→DragaliaAPI.Shared.Definitions.Enums.ExpeditionStateDragaliaAPI.Database.Entities.DbPlayerDmodeServitorPassive→DragaliaAPI.Shared.Definitions.Enums.DmodeServitorPassiveTypeDragaliaAPI.Database.Entities.DbPlayerDragonData→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Database.Entities.DbPlayerDragonGift→DragaliaAPI.Shared.Definitions.Enums.DragonGiftsDragaliaAPI.Database.Entities.DbPlayerDragonReliability→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Database.Entities.DbPlayerHelper→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Database.Entities.DbPlayerHelper→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Entities.DbPlayerHelper→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Database.Entities.DbPlayerMaterial→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Database.Entities.DbPlayerPresent→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Database.Entities.DbPlayerPresentHistory→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Database.Entities.DbPlayerShopPurchase→DragaliaAPI.Shared.Definitions.Enums.PurchaseShopTypeDragaliaAPI.Database.Entities.DbPlayerStoryState→DragaliaAPI.Shared.Definitions.Enums.StoryStateDragaliaAPI.Database.Entities.DbPlayerStoryState→DragaliaAPI.Shared.Definitions.Enums.StoryTypes
- Direction
- Database.Entities uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Database.Entities, while a change to Database.Entities can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Database.Entities uses a module listed above it, which is the healthy direction.
5→2 Features.Shared.Options uses Shared.Definitions.Enums✕
- Connections
- 1 pair of types, where a type in Features.Shared.Options uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Shared.Options.ItemSummonOddsEntry→DragaliaAPI.Shared.Definitions.Enums.EntityTypes
- Direction
- Features.Shared.Options uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Shared.Options, while a change to Features.Shared.Options can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Shared.Options uses a module listed above it, which is the healthy direction.
6→1 Infrastructure uses Infrastructure.Results✕
- Connections
- 3 pairs of types, where a type in Infrastructure uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Infrastructure.DragaliaControllerBaseCore→DragaliaAPI.Infrastructure.Results.ResultCodeDragaliaAPI.Infrastructure.DragaliaException→DragaliaAPI.Infrastructure.Results.ResultCodeDragaliaAPI.Infrastructure.HttpContextExtensions→DragaliaAPI.Infrastructure.Results.ResultCode
- Direction
- Infrastructure uses Infrastructure.Results, so a change to Infrastructure.Results can break Infrastructure, while a change to Infrastructure can't break Infrastructure.Results.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
7→2 Shared.MasterAsset.Models uses Shared.Definitions.Enums✕
- Connections
- 57 pairs of types, where a type in Shared.MasterAsset.Models uses a type in Shared.Definitions.Enums. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DragaliaAPI.Shared.MasterAsset.Models.AbilityCrest→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Shared.MasterAsset.Models.AbilityCrest→DragaliaAPI.Shared.Definitions.Enums.BuildupPieceTypesDragaliaAPI.Shared.MasterAsset.Models.AbilityCrest→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Shared.MasterAsset.Models.AbilityCrest→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Shared.MasterAsset.Models.AbilityCrestBuildupGroup→DragaliaAPI.Shared.Definitions.Enums.BuildupPieceTypesDragaliaAPI.Shared.MasterAsset.Models.AbilityCrestBuildupGroup→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Shared.MasterAsset.Models.AbilityCrestBuildupLevel→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Shared.MasterAsset.Models.AbilityData→DragaliaAPI.Shared.Definitions.Enums.AbilityTypesDragaliaAPI.Shared.MasterAsset.Models.AbilityData→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Shared.MasterAsset.Models.AbilityData→DragaliaAPI.Shared.Definitions.Enums.WeaponTypesDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.ManaNodesDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Shared.MasterAsset.Models.CharaData→DragaliaAPI.Shared.Definitions.Enums.WeaponTypesDragaliaAPI.Shared.MasterAsset.Models.DragonData→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Shared.MasterAsset.Models.DragonData→DragaliaAPI.Shared.Definitions.Enums.DragonLimitBreakTypesDragaliaAPI.Shared.MasterAsset.Models.DragonData→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Shared.MasterAsset.Models.DragonData→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Shared.MasterAsset.Models.EmblemData→DragaliaAPI.Shared.Definitions.Enums.EmblemsDragaliaAPI.Shared.MasterAsset.Models.EmblemData→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Shared.MasterAsset.Models.FortPlantDetail→DragaliaAPI.Shared.Definitions.Enums.EventEffectTypesDragaliaAPI.Shared.MasterAsset.Models.FortPlantDetail→DragaliaAPI.Shared.Definitions.Enums.FortEffectTypesDragaliaAPI.Shared.MasterAsset.Models.FortPlantDetail→DragaliaAPI.Shared.Definitions.Enums.FortPlants
- Direction
- Shared.MasterAsset.Models uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Shared.MasterAsset.Models, while a change to Shared.MasterAsset.Models can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Shared.MasterAsset.Models uses a module listed above it, which is the healthy direction.
8→3 Database uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Database uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Database.ApiContext→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.StubPlayerIdentityService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Database uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Database, while a change to Database can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Database uses a module listed above it, which is the healthy direction.
8→4 Database uses Database.Entities✕
- Connections
- 64 pairs of types, where a type in Database uses a type in Database.Entities. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbAbilityCrestSetDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbCompletedDailyMissionDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbEmblemDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbEquippedStampDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbFortBuildDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbFortDetailDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbLoginBonusDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbNewsItemDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPartyPowerDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerBannerDataDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerCharaHonorDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDiamondDataDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDmodeCharaDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDmodeDungeonDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDmodeExpeditionDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDmodeInfoDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDmodeServitorPassiveDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDragonGiftDragaliaAPI.Database.ApiContext→DragaliaAPI.Database.Entities.DbPlayerDragonReliability
- Direction
- Database uses Database.Entities, so a change to Database.Entities can break Database, while a change to Database can't break Database.Entities.
- Position
- Below the diagonal: Database uses a module listed above it, which is the healthy direction.
9→2 Models.Generated uses Shared.Definitions.Enums✕
- Connections
- 11 pairs of types, where a type in Models.Generated uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Models.Generated.AtgenBoxSummonDetail→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Models.Generated.AtgenDropAll→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Models.Generated.CharaBuildupManaRequest→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Models.Generated.CharaLimitBreakAndBuildupManaRequest→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Models.Generated.DragonList→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Models.Generated.IngameResultData→DragaliaAPI.Shared.Definitions.Enums.QuestPlayTypeDragaliaAPI.Models.Generated.PartySettingList→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Models.Generated.PartySettingList→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Models.Generated.PartySettingList→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Models.Generated.UserData→DragaliaAPI.Shared.Definitions.Enums.EmblemsDragaliaAPI.Models.Generated.WeaponBodyList→DragaliaAPI.Shared.Definitions.Enums.WeaponBodies
- Direction
- Models.Generated uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Models.Generated, while a change to Models.Generated can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Models.Generated uses a module listed above it, which is the healthy direction.
9→4 Models.Generated uses Database.Entities✕
- Connections
- 3 pairs of types, where a type in Models.Generated uses a type in Database.Entities.
- The types involved
DragaliaAPI.Models.Generated.BuildEventRewardList→DragaliaAPI.Database.Entities.DbPlayerEventRewardDragaliaAPI.Models.Generated.RaidEventRewardList→DragaliaAPI.Database.Entities.DbPlayerEventRewardDragaliaAPI.Models.Generated.UserEventLocationRewardList→DragaliaAPI.Database.Entities.DbPlayerEventReward
- Direction
- Models.Generated uses Database.Entities, so a change to Database.Entities can break Models.Generated, while a change to Models.Generated can't break Database.Entities.
- Position
- Below the diagonal: Models.Generated uses a module listed above it, which is the healthy direction.
9→22 Models.Generated uses Features.Event part of a loop✕
- Connections
- 9 pairs of types, where a type in Models.Generated uses a type in Features.Event.
- The types involved
DragaliaAPI.Models.Generated.BuildEventRewardList→DragaliaAPI.Features.Event.IEventRewardListDragaliaAPI.Models.Generated.EventSummonExecRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.EventSummonGetDataRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.EventSummonResetRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.RaidEventEntryRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.RaidEventGetEventDataRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.RaidEventReceiveRaidPointRewardRequest→DragaliaAPI.Features.Event.IEventRequestDragaliaAPI.Models.Generated.RaidEventRewardList→DragaliaAPI.Features.Event.IEventRewardListDragaliaAPI.Models.Generated.UserEventLocationRewardList→DragaliaAPI.Features.Event.IEventRewardList
- Direction
- Models.Generated uses Features.Event, so a change to Features.Event can break Models.Generated, while a change to Models.Generated can't break Features.Event.
- 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→36 Models.Generated uses Features.Missions part of a loop✕
- Connections
- 9 pairs of types, where a type in Models.Generated uses a type in Features.Missions.
- The types involved
DragaliaAPI.Models.Generated.MissionGetMissionListResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveAlbumRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveBeginnerRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveDailyRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveMainStoryRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveMemoryEventRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveNormalRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceivePeriodRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponseDragaliaAPI.Models.Generated.MissionReceiveSpecialRewardResponse→DragaliaAPI.Features.Missions.INormalMissionEndpointResponse
- Direction
- Models.Generated uses Features.Missions, so a change to Features.Missions can break Models.Generated, while a change to Models.Generated can't break Features.Missions.
- 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→2 Database.Repositories uses Shared.Definitions.Enums✕
- Connections
- 15 pairs of types, where a type in Database.Repositories uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Database.Repositories.IInventoryRepository→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Shared.Definitions.Enums.TalismansDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Database.Repositories.InventoryRepository→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Database.Repositories.Log→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Shared.Definitions.Enums.TalismansDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Database.Repositories.WeaponRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Database.Repositories.WeaponRepository→DragaliaAPI.Shared.Definitions.Enums.WeaponBodies
- Direction
- Database.Repositories uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Database.Repositories, while a change to Database.Repositories can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Database.Repositories uses a module listed above it, which is the healthy direction.
10→3 Database.Repositories uses Shared.PlayerDetails✕
- Connections
- 6 pairs of types, where a type in Database.Repositories uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Database.Repositories.InventoryRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.Repositories.PartyRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.Repositories.QuestRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.Repositories.UserDataRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Database.Repositories.WeaponRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Database.Repositories uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Database.Repositories, while a change to Database.Repositories can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Database.Repositories uses a module listed above it, which is the healthy direction.
10→4 Database.Repositories uses Database.Entities✕
- Connections
- 33 pairs of types, where a type in Database.Repositories uses a type in Database.Entities. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DragaliaAPI.Database.Repositories.IInventoryRepository→DragaliaAPI.Database.Entities.DbPlayerMaterialDragaliaAPI.Database.Repositories.IPartyRepository→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Database.Repositories.IPartyRepository→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Database.Repositories.IQuestRepository→DragaliaAPI.Database.Entities.DbQuestDragaliaAPI.Database.Repositories.IQuestRepository→DragaliaAPI.Database.Entities.DbQuestEventDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbPlayerDragonReliabilityDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbSetUnitDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbTalismanDragaliaAPI.Database.Repositories.IUnitRepository→DragaliaAPI.Database.Entities.DbWeaponBodyDragaliaAPI.Database.Repositories.IUserDataRepository→DragaliaAPI.Database.Entities.DbPlayerUserDataDragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Database.Entities.DbWeaponBodyDragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Database.Entities.DbWeaponPassiveAbilityDragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Database.Entities.DbWeaponSkinDragaliaAPI.Database.Repositories.InventoryRepository→DragaliaAPI.Database.Entities.DbPlayerMaterialDragaliaAPI.Database.Repositories.Log→DragaliaAPI.Database.Entities.DbPlayerMaterialDragaliaAPI.Database.Repositories.PartyRepository→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Database.Repositories.PartyRepository→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Database.Repositories.QuestRepository→DragaliaAPI.Database.Entities.DbQuestDragaliaAPI.Database.Repositories.QuestRepository→DragaliaAPI.Database.Entities.DbQuestEventDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Database.Entities.DbPlayerDragonData
- Direction
- Database.Repositories uses Database.Entities, so a change to Database.Entities can break Database.Repositories, while a change to Database.Repositories can't break Database.Entities.
- Position
- Below the diagonal: Database.Repositories uses a module listed above it, which is the healthy direction.
10→7 Database.Repositories uses Shared.MasterAsset.Models✕
- Connections
- 2 pairs of types, where a type in Database.Repositories uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Database.Repositories.IWeaponRepository→DragaliaAPI.Shared.MasterAsset.Models.WeaponPassiveAbilityDragaliaAPI.Database.Repositories.WeaponRepository→DragaliaAPI.Shared.MasterAsset.Models.WeaponPassiveAbility
- Direction
- Database.Repositories uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Database.Repositories, while a change to Database.Repositories can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Database.Repositories uses a module listed above it, which is the healthy direction.
10→8 Database.Repositories uses Database✕
- Connections
- 7 pairs of types, where a type in Database.Repositories uses a type in Database.
- The types involved
DragaliaAPI.Database.Repositories.BaseRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.InventoryRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.PartyRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.QuestRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.UnitRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.UserDataRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Database.Repositories.WeaponRepository→DragaliaAPI.Database.ApiContext
- Direction
- Database.Repositories uses Database, so a change to Database can break Database.Repositories, while a change to Database.Repositories can't break Database.
- Position
- Below the diagonal: Database.Repositories uses a module listed above it, which is the healthy direction.
11→1 Features.Present uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Present uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Present.PresentController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Present uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Present, while a change to Features.Present can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→2 Features.Present uses Shared.Definitions.Enums✕
- Connections
- 1 pair of types, where a type in Features.Present uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Present.Present→DragaliaAPI.Shared.Definitions.Enums.EntityTypes
- Direction
- Features.Present uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Present, while a change to Features.Present can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→3 Features.Present uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Present uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Present.PresentService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Present uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Present, while a change to Features.Present can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→4 Features.Present uses Database.Entities✕
- Connections
- 6 pairs of types, where a type in Features.Present uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Present.IPresentRepository→DragaliaAPI.Database.Entities.DbPlayerPresentDragaliaAPI.Features.Present.IPresentRepository→DragaliaAPI.Database.Entities.DbPlayerPresentHistoryDragaliaAPI.Features.Present.Log→DragaliaAPI.Database.Entities.DbPlayerPresentDragaliaAPI.Features.Present.MappingExtensions→DragaliaAPI.Database.Entities.DbPlayerPresentDragaliaAPI.Features.Present.MappingExtensions→DragaliaAPI.Database.Entities.DbPlayerPresentHistoryDragaliaAPI.Features.Present.Present→DragaliaAPI.Database.Entities.DbPlayerPresent
- Direction
- Features.Present uses Database.Entities, so a change to Database.Entities can break Features.Present, while a change to Features.Present can't break Database.Entities.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→6 Features.Present uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Present uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Present.PresentController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Present uses Infrastructure, so a change to Infrastructure can break Features.Present, while a change to Features.Present can't break Infrastructure.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→8 Features.Present uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Present uses a type in Database.
- The types involved
DragaliaAPI.Features.Present.PresentControllerService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Present.PresentService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Present uses Database, so a change to Database can break Features.Present, while a change to Features.Present can't break Database.
- Position
- Below the diagonal: Features.Present uses a module listed above it, which is the healthy direction.
11→16 Features.Present uses Features.Shared.Reward part of a loop✕
- Connections
- 3 pairs of types, where a type in Features.Present uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Present.Present→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Present.PresentController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Present.PresentControllerService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Present uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Present, while a change to Features.Present can't break Features.Shared.Reward.
- 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→30 Features.Present uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Present uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Present.PresentController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Present uses Features.Shared, so a change to Features.Shared can break Features.Present, while a change to Features.Present can't break Features.Shared.
- 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→1 Features.CoOp uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.CoOp uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.CoOp.MatchingController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.CoOp uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.CoOp, while a change to Features.CoOp can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.CoOp uses a module listed above it, which is the healthy direction.
12→3 Features.CoOp uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Features.CoOp uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.CoOp.HeroParamService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.CoOp.MatchingService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.CoOp uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.CoOp, while a change to Features.CoOp can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.CoOp uses a module listed above it, which is the healthy direction.
12→6 Features.CoOp uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.CoOp uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.CoOp.MatchingController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.CoOp uses Infrastructure, so a change to Infrastructure can break Features.CoOp, while a change to Features.CoOp can't break Infrastructure.
- Position
- Below the diagonal: Features.CoOp uses a module listed above it, which is the healthy direction.
12→8 Features.CoOp uses Database✕
- Connections
- 1 pair of types, where a type in Features.CoOp uses a type in Database.
- The types involved
DragaliaAPI.Features.CoOp.MatchingService→DragaliaAPI.Database.ApiContext
- Direction
- Features.CoOp uses Database, so a change to Database can break Features.CoOp, while a change to Features.CoOp can't break Database.
- Position
- Below the diagonal: Features.CoOp uses a module listed above it, which is the healthy direction.
12→10 Features.CoOp uses Database.Repositories✕
- Connections
- 4 pairs of types, where a type in Features.CoOp uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.CoOp.HeroParamService→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.CoOp.HeroParamService→DragaliaAPI.Database.Repositories.IWeaponRepositoryDragaliaAPI.Features.CoOp.MatchingService→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.CoOp.MatchingService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.CoOp uses Database.Repositories, so a change to Database.Repositories can break Features.CoOp, while a change to Features.CoOp can't break Database.Repositories.
- Position
- Below the diagonal: Features.CoOp uses a module listed above it, which is the healthy direction.
12→23 Features.CoOp uses Features.Dungeon part of a loop✕
- Connections
- 1 pair of types, where a type in Features.CoOp uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.CoOp.HeroParamService→DragaliaAPI.Features.Dungeon.IDungeonRepository
- Direction
- Features.CoOp uses Features.Dungeon, so a change to Features.Dungeon can break Features.CoOp, while a change to Features.CoOp can't break Features.Dungeon.
- 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→32 Features.CoOp uses Features.Fort part of a loop✕
- Connections
- 1 pair of types, where a type in Features.CoOp uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.CoOp.HeroParamService→DragaliaAPI.Features.Fort.IBonusService
- Direction
- Features.CoOp uses Features.Fort, so a change to Features.Fort can break Features.CoOp, while a change to Features.CoOp can't break Features.Fort.
- 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→1 Features.Friends uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Friends uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Friends.FriendController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Friends uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Friends, while a change to Features.Friends can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→2 Features.Friends uses Shared.Definitions.Enums✕
- Connections
- 1 pair of types, where a type in Features.Friends uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Friends.UserDataProjection→DragaliaAPI.Shared.Definitions.Enums.Emblems
- Direction
- Features.Friends uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Friends, while a change to Features.Friends can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→3 Features.Friends uses Shared.PlayerDetails✕
- Connections
- 5 pairs of types, where a type in Features.Friends uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Friends.FriendController→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Friends.FriendNotificationService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Friends.FriendService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Friends.HelperService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Friends.RealHelperDataService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Friends uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Friends, while a change to Features.Friends can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→4 Features.Friends uses Database.Entities✕
- Connections
- 4 pairs of types, where a type in Features.Friends uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Friends.FriendNotificationService→DragaliaAPI.Database.Entities.DbPlayerDragaliaAPI.Features.Friends.FriendService→DragaliaAPI.Database.Entities.DbPlayerDragaliaAPI.Features.Friends.FriendService→DragaliaAPI.Database.Entities.DbPlayerFriendshipDragaliaAPI.Features.Friends.MappingExtensions→DragaliaAPI.Database.Entities.DbPlayerHelper
- Direction
- Features.Friends uses Database.Entities, so a change to Database.Entities can break Features.Friends, while a change to Features.Friends can't break Database.Entities.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→6 Features.Friends uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Friends uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Friends.FriendController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Friends uses Infrastructure, so a change to Infrastructure can break Features.Friends, while a change to Features.Friends can't break Infrastructure.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→8 Features.Friends uses Database✕
- Connections
- 4 pairs of types, where a type in Features.Friends uses a type in Database.
- The types involved
DragaliaAPI.Features.Friends.FriendNotificationService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Friends.FriendService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Friends.HelperService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Friends.RealHelperDataService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Friends uses Database, so a change to Database can break Features.Friends, while a change to Features.Friends can't break Database.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→9 Features.Friends uses Models.Generated✕
- Connections
- 2 pairs of types, where a type in Features.Friends uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Friends.FriendController→DragaliaAPI.Models.Generated.FriendReplyRequestDragaliaAPI.Features.Friends.FriendService→DragaliaAPI.Models.Generated.FriendReplyType
- Direction
- Features.Friends uses Models.Generated, so a change to Models.Generated can break Features.Friends, while a change to Features.Friends can't break Models.Generated.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→10 Features.Friends uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Friends uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Friends.HelperService→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.Friends.HelperService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Friends uses Database.Repositories, so a change to Database.Repositories can break Features.Friends, while a change to Features.Friends can't break Database.Repositories.
- Position
- Below the diagonal: Features.Friends uses a module listed above it, which is the healthy direction.
13→23 Features.Friends uses Features.Dungeon part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Friends uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.Friends.HelperService→DragaliaAPI.Features.Dungeon.IDungeonRepository
- Direction
- Features.Friends uses Features.Dungeon, so a change to Features.Dungeon can break Features.Friends, while a change to Features.Friends can't break Features.Dungeon.
- 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→30 Features.Friends uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Friends uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Friends.FriendController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Friends uses Features.Shared, so a change to Features.Shared can break Features.Friends, while a change to Features.Friends can't break Features.Shared.
- 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→32 Features.Friends uses Features.Fort part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Friends uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Friends.RealHelperDataService→DragaliaAPI.Features.Fort.IBonusServiceDragaliaAPI.Features.Friends.StaticHelperDataService→DragaliaAPI.Features.Fort.IBonusService
- Direction
- Features.Friends uses Features.Fort, so a change to Features.Fort can break Features.Friends, while a change to Features.Friends can't break Features.Fort.
- 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→10 Features.Player uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Player uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Player.UserService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Player uses Database.Repositories, so a change to Database.Repositories can break Features.Player, while a change to Features.Player can't break Database.Repositories.
- Position
- Below the diagonal: Features.Player uses a module listed above it, which is the healthy direction.
14→11 Features.Player uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Player uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Player.UserService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Player uses Features.Present, so a change to Features.Present can break Features.Player, while a change to Features.Player can't break Features.Present.
- Position
- Below the diagonal: Features.Player uses a module listed above it, which is the healthy direction.
15→2 Features.Shared.Reward.Handlers uses Shared.Definitions.Enums✕
- Connections
- 18 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.AbilityCrestRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.CharaHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.DiamantiumHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.DmodePointRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Shared.Definitions.Enums.DragonGiftsDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.DragonHandler→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Shared.Reward.Handlers.DragonHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.EmblemRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.FafnirMedalRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.HustleHammerHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.IRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.StampRewardHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.SummonTicketHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.WeaponBodyHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.WeaponSkinHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.Handlers.WyrmiteHandler→DragaliaAPI.Shared.Definitions.Enums.EntityTypes
- Direction
- Features.Shared.Reward.Handlers uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→3 Features.Shared.Reward.Handlers uses Shared.PlayerDetails✕
- Connections
- 5 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.CharaHandler→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Shared.Reward.Handlers.DragonHandler→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Shared.Reward.Handlers.SummonTicketHandler→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Shared.Reward.Handlers.WeaponBodyHandler→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Shared.Reward.Handlers uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→4 Features.Shared.Reward.Handlers uses Database.Entities✕
- Connections
- 6 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.DiamantiumHandler→DragaliaAPI.Database.Entities.DbPlayerDiamondDataDragaliaAPI.Features.Shared.Reward.Handlers.DmodePointRewardHandler→DragaliaAPI.Database.Entities.DbPlayerDmodeInfoDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Database.Entities.DbPlayerDragonGiftDragaliaAPI.Features.Shared.Reward.Handlers.HustleHammerHandler→DragaliaAPI.Database.Entities.DbPlayerUserDataDragaliaAPI.Features.Shared.Reward.Handlers.SummonTicketHandler→DragaliaAPI.Database.Entities.DbSummonTicketDragaliaAPI.Features.Shared.Reward.Handlers.WyrmiteHandler→DragaliaAPI.Database.Entities.DbPlayerUserData
- Direction
- Features.Shared.Reward.Handlers uses Database.Entities, so a change to Database.Entities can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Database.Entities.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→8 Features.Shared.Reward.Handlers uses Database✕
- Connections
- 9 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Database.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.CharaHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.DiamantiumHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.DmodePointRewardHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.DragonHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.HustleHammerHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.SummonTicketHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.WeaponBodyHandler→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shared.Reward.Handlers.WyrmiteHandler→DragaliaAPI.Database.ApiContext
- Direction
- Features.Shared.Reward.Handlers uses Database, so a change to Database can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Database.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→10 Features.Shared.Reward.Handlers uses Database.Repositories✕
- Connections
- 3 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Shared.Reward.Handlers.WeaponSkinHandler→DragaliaAPI.Database.Repositories.IWeaponRepository
- Direction
- Features.Shared.Reward.Handlers uses Database.Repositories, so a change to Database.Repositories can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Database.Repositories.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→14 Features.Shared.Reward.Handlers uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Shared.Reward.Handlers uses Features.Player, so a change to Features.Player can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.Player.
- Position
- Below the diagonal: Features.Shared.Reward.Handlers uses a module listed above it, which is the healthy direction.
15→16 Features.Shared.Reward.Handlers uses Features.Shared.Reward part of a loop✕
- Connections
- 21 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.AbilityCrestRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.CharaHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.DiamantiumHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.DmodePointRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.DragonGiftHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.DragonHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.EmblemRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.FafnirMedalRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Shared.Reward.RewardServiceDragaliaAPI.Features.Shared.Reward.Handlers.GrantReturn→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.GrantReturn→DragaliaAPI.Features.Shared.Reward.RewardGrantResultDragaliaAPI.Features.Shared.Reward.Handlers.HustleHammerHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.IBatchRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.IRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.Log→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.StampRewardHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.SummonTicketHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.WeaponBodyHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.WeaponSkinHandler→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shared.Reward.Handlers.WyrmiteHandler→DragaliaAPI.Features.Shared.Reward.Entity
- Direction
- Features.Shared.Reward.Handlers uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.Shared.Reward.
- 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→22 Features.Shared.Reward.Handlers uses Features.Event part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Shared.Reward.Handlers uses Features.Event, so a change to Features.Event can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.Event.
- 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→29 Features.Shared.Reward.Handlers uses Features.Dmode part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.Dmode.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.DmodePointRewardHandler→DragaliaAPI.Features.Dmode.IDmodeRepositoryDragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Dmode.IDmodeRepository
- Direction
- Features.Shared.Reward.Handlers uses Features.Dmode, so a change to Features.Dmode can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.Dmode.
- 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→32 Features.Shared.Reward.Handlers uses Features.Fort part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.GenericRewardHandler→DragaliaAPI.Features.Fort.IFortRepository
- Direction
- Features.Shared.Reward.Handlers uses Features.Fort, so a change to Features.Fort can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.Fort.
- 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→37 Features.Shared.Reward.Handlers uses Features.AbilityCrests part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward.Handlers uses a type in Features.AbilityCrests.
- The types involved
DragaliaAPI.Features.Shared.Reward.Handlers.AbilityCrestRewardHandler→DragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository
- Direction
- Features.Shared.Reward.Handlers uses Features.AbilityCrests, so a change to Features.AbilityCrests can break Features.Shared.Reward.Handlers, while a change to Features.Shared.Reward.Handlers can't break Features.AbilityCrests.
- 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→2 Features.Shared.Reward uses Shared.Definitions.Enums✕
- Connections
- 5 pairs of types, where a type in Features.Shared.Reward uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Shared.Reward.Entity→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.IRewardService→DragaliaAPI.Shared.Definitions.Enums.TalismansDragaliaAPI.Features.Shared.Reward.Log→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Shared.Definitions.Enums.Talismans
- Direction
- Features.Shared.Reward uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Shared.Reward, while a change to Features.Shared.Reward can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Shared.Reward uses a module listed above it, which is the healthy direction.
16→4 Features.Shared.Reward uses Database.Entities✕
- Connections
- 2 pairs of types, where a type in Features.Shared.Reward uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Shared.Reward.IRewardService→DragaliaAPI.Database.Entities.DbTalismanDragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Database.Entities.DbTalisman
- Direction
- Features.Shared.Reward uses Database.Entities, so a change to Database.Entities can break Features.Shared.Reward, while a change to Features.Shared.Reward can't break Database.Entities.
- Position
- Below the diagonal: Features.Shared.Reward uses a module listed above it, which is the healthy direction.
16→9 Features.Shared.Reward uses Models.Generated✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Shared.Reward.Entity→DragaliaAPI.Models.Generated.AtgenDropAll
- Direction
- Features.Shared.Reward uses Models.Generated, so a change to Models.Generated can break Features.Shared.Reward, while a change to Features.Shared.Reward can't break Models.Generated.
- Position
- Below the diagonal: Features.Shared.Reward uses a module listed above it, which is the healthy direction.
16→10 Features.Shared.Reward uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Shared.Reward uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Database.Repositories.IUnitRepository
- Direction
- Features.Shared.Reward uses Database.Repositories, so a change to Database.Repositories can break Features.Shared.Reward, while a change to Features.Shared.Reward can't break Database.Repositories.
- Position
- Below the diagonal: Features.Shared.Reward uses a module listed above it, which is the healthy direction.
16→15 Features.Shared.Reward uses Features.Shared.Reward.Handlers✕
- Connections
- 3 pairs of types, where a type in Features.Shared.Reward uses a type in Features.Shared.Reward.Handlers.
- The types involved
DragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Features.Shared.Reward.Handlers.GrantReturnDragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Features.Shared.Reward.Handlers.IBatchRewardHandlerDragaliaAPI.Features.Shared.Reward.RewardService→DragaliaAPI.Features.Shared.Reward.Handlers.IRewardHandler
- Direction
- Features.Shared.Reward uses Features.Shared.Reward.Handlers, so a change to Features.Shared.Reward.Handlers can break Features.Shared.Reward, while a change to Features.Shared.Reward can't break Features.Shared.Reward.Handlers.
- Position
- Below the diagonal: Features.Shared.Reward uses a module listed above it, which is the healthy direction.
17→1 Features.Quest uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Quest.QuestController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Quest uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Quest, while a change to Features.Quest can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→3 Features.Quest uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Quest.QuestCacheService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Quest.QuestTreasureService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Quest uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Quest, while a change to Features.Quest can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→4 Features.Quest uses Database.Entities✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Database.Entities.DbQuestDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Database.Entities.DbQuestEvent
- Direction
- Features.Quest uses Database.Entities, so a change to Database.Entities can break Features.Quest, while a change to Features.Quest can't break Database.Entities.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→6 Features.Quest uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Quest.QuestController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Quest uses Infrastructure, so a change to Infrastructure can break Features.Quest, while a change to Features.Quest can't break Infrastructure.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→7 Features.Quest uses Shared.MasterAsset.Models✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Shared.MasterAsset.Models.QuestDataDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Shared.MasterAsset.Models.QuestEvent
- Direction
- Features.Quest uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Quest, while a change to Features.Quest can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→8 Features.Quest uses Database✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Database.
- The types involved
DragaliaAPI.Features.Quest.QuestTreasureService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Quest uses Database, so a change to Database can break Features.Quest, while a change to Features.Quest can't break Database.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→9 Features.Quest uses Models.Generated✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Quest.IQuestService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Models.Generated.PlayRecord
- Direction
- Features.Quest uses Models.Generated, so a change to Models.Generated can break Features.Quest, while a change to Features.Quest can't break Models.Generated.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→10 Features.Quest uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Database.Repositories.IQuestRepositoryDragaliaAPI.Features.Quest.QuestTreasureService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Quest uses Database.Repositories, so a change to Database.Repositories can break Features.Quest, while a change to Features.Quest can't break Database.Repositories.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→13 Features.Quest uses Features.Friends✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Features.Friends.
- The types involved
DragaliaAPI.Features.Quest.QuestController→DragaliaAPI.Features.Friends.IHelperService
- Direction
- Features.Quest uses Features.Friends, so a change to Features.Friends can break Features.Quest, while a change to Features.Quest can't break Features.Friends.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→14 Features.Quest uses Features.Player✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Quest.IQuestService→DragaliaAPI.Features.Player.StaminaTypeDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Features.Player.StaminaType
- Direction
- Features.Quest uses Features.Player, so a change to Features.Player can break Features.Quest, while a change to Features.Quest can't break Features.Player.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→16 Features.Quest uses Features.Shared.Reward✕
- Connections
- 3 pairs of types, where a type in Features.Quest uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Quest.QuestTreasureService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Quest uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Quest, while a change to Features.Quest can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Quest uses a module listed above it, which is the healthy direction.
17→23 Features.Quest uses Features.Dungeon part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.Quest.IQuestService→DragaliaAPI.Features.Dungeon.DungeonSessionDragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Features.Dungeon.DungeonSession
- Direction
- Features.Quest uses Features.Dungeon, so a change to Features.Dungeon can break Features.Quest, while a change to Features.Quest can't break Features.Dungeon.
- 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→26 Features.Quest uses Features.Story part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Quest.QuestController→DragaliaAPI.Features.Story.IStoryService
- Direction
- Features.Quest uses Features.Story, so a change to Features.Story can break Features.Quest, while a change to Features.Quest can't break Features.Story.
- 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→30 Features.Quest uses Features.Shared part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Quest uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Quest.QuestController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Quest.QuestTreasureService→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Quest uses Features.Shared, so a change to Features.Shared can break Features.Quest, while a change to Features.Quest can't break Features.Shared.
- 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→36 Features.Quest uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Quest uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Quest.QuestService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Quest uses Features.Missions, so a change to Features.Missions can break Features.Quest, while a change to Features.Quest can't break Features.Missions.
- 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→1 Features.Shop uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Shop.ShopController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Shop uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Shop, while a change to Features.Shop can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→2 Features.Shop uses Shared.Definitions.Enums✕
- Connections
- 9 pairs of types, where a type in Features.Shop uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Shop.IPaymentService→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Features.Shop.IPaymentService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Shop.IShopService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Shop.IShopService→DragaliaAPI.Shared.Definitions.Enums.PurchaseShopTypeDragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Shop.ShopService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Shop.ShopService→DragaliaAPI.Shared.Definitions.Enums.PurchaseShopTypeDragaliaAPI.Features.Shop.ShopTypeExtensions→DragaliaAPI.Shared.Definitions.Enums.PurchaseShopType
- Direction
- Features.Shop uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Shop, while a change to Features.Shop can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→3 Features.Shop uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Shop.ShopRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Shop uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Shop, while a change to Features.Shop can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→4 Features.Shop uses Database.Entities✕
- Connections
- 4 pairs of types, where a type in Features.Shop uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Shop.IShopRepository→DragaliaAPI.Database.Entities.DbPlayerShopInfoDragaliaAPI.Features.Shop.IShopRepository→DragaliaAPI.Database.Entities.DbPlayerShopPurchaseDragaliaAPI.Features.Shop.ShopRepository→DragaliaAPI.Database.Entities.DbPlayerShopInfoDragaliaAPI.Features.Shop.ShopRepository→DragaliaAPI.Database.Entities.DbPlayerShopPurchase
- Direction
- Features.Shop uses Database.Entities, so a change to Database.Entities can break Features.Shop, while a change to Features.Shop can't break Database.Entities.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→5 Features.Shop uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Shop.ItemSummonService→DragaliaAPI.Features.Shared.Options.ItemSummonConfig
- Direction
- Features.Shop uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Shop, while a change to Features.Shop can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→6 Features.Shop uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Shop.ShopController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Shop uses Infrastructure, so a change to Infrastructure can break Features.Shop, while a change to Features.Shop can't break Infrastructure.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→8 Features.Shop uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Shop uses a type in Database.
- The types involved
DragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Shop.ShopRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Shop uses Database, so a change to Database can break Features.Shop, while a change to Features.Shop can't break Database.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→10 Features.Shop uses Database.Repositories✕
- Connections
- 3 pairs of types, where a type in Features.Shop uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Shop.ShopService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Shop uses Database.Repositories, so a change to Database.Repositories can break Features.Shop, while a change to Features.Shop can't break Database.Repositories.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→14 Features.Shop uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Shop.ShopService→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Shop uses Features.Player, so a change to Features.Player can break Features.Shop, while a change to Features.Shop can't break Features.Player.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→16 Features.Shop uses Features.Shared.Reward✕
- Connections
- 5 pairs of types, where a type in Features.Shop uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Shop.IPaymentService→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shop.ItemSummonService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Shop.ShopController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Shop.ShopService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Shop uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Shop, while a change to Features.Shop can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Shop uses a module listed above it, which is the healthy direction.
18→22 Features.Shop uses Features.Event part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Shop uses Features.Event, so a change to Features.Event can break Features.Shop, while a change to Features.Shop can't break Features.Event.
- 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→29 Features.Shop uses Features.Dmode part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Dmode.
- The types involved
DragaliaAPI.Features.Shop.PaymentService→DragaliaAPI.Features.Dmode.IDmodeRepository
- Direction
- Features.Shop uses Features.Dmode, so a change to Features.Dmode can break Features.Shop, while a change to Features.Shop can't break Features.Dmode.
- 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→30 Features.Shop uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Shop.ShopController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Shop uses Features.Shared, so a change to Features.Shared can break Features.Shop, while a change to Features.Shop can't break Features.Shared.
- 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→36 Features.Shop uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Shop uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Shop.ItemSummonService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Shop uses Features.Missions, so a change to Features.Missions can break Features.Shop, while a change to Features.Shop can't break Features.Missions.
- 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.
19→1 Features.Chara uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Chara uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Chara, while a change to Features.Chara can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→2 Features.Chara uses Shared.Definitions.Enums✕
- Connections
- 4 pairs of types, where a type in Features.Chara uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Chara.CharaService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Chara.ICharaService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Chara.Log→DragaliaAPI.Shared.Definitions.Enums.Charas
- Direction
- Features.Chara uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Chara, while a change to Features.Chara can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→4 Features.Chara uses Database.Entities✕
- Connections
- 3 pairs of types, where a type in Features.Chara uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Database.Entities.DbSetUnitDragaliaAPI.Features.Chara.Log→DragaliaAPI.Database.Entities.DbPlayerCharaData
- Direction
- Features.Chara uses Database.Entities, so a change to Database.Entities can break Features.Chara, while a change to Features.Chara can't break Database.Entities.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→5 Features.Chara uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Shared.Options.EventOptions
- Direction
- Features.Chara uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Chara, while a change to Features.Chara can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→6 Features.Chara uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Chara uses Infrastructure, so a change to Infrastructure can break Features.Chara, while a change to Features.Chara can't break Infrastructure.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→8 Features.Chara uses Database✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Database.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Database.ApiContext
- Direction
- Features.Chara uses Database, so a change to Database can break Features.Chara, while a change to Features.Chara can't break Database.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→9 Features.Chara uses Models.Generated✕
- Connections
- 3 pairs of types, where a type in Features.Chara uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Models.Generated.CharaBuildupManaRequestDragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Models.Generated.CharaLimitBreakAndBuildupManaRequestDragaliaAPI.Features.Chara.Log→DragaliaAPI.Models.Generated.CharaBuildupManaRequest
- Direction
- Features.Chara uses Models.Generated, so a change to Models.Generated can break Features.Chara, while a change to Features.Chara can't break Models.Generated.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→10 Features.Chara uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Chara uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Database.Repositories.IUnitRepositoryDragaliaAPI.Features.Chara.CharaService→DragaliaAPI.Database.Repositories.IUnitRepository
- Direction
- Features.Chara uses Database.Repositories, so a change to Database.Repositories can break Features.Chara, while a change to Features.Chara can't break Database.Repositories.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→16 Features.Chara uses Features.Shared.Reward✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Chara uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Chara, while a change to Features.Chara can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→18 Features.Chara uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Chara uses Features.Shop, so a change to Features.Shop can break Features.Chara, while a change to Features.Chara can't break Features.Shop.
- Position
- Below the diagonal: Features.Chara uses a module listed above it, which is the healthy direction.
19→26 Features.Chara uses Features.Story part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Story.IStoryRepository
- Direction
- Features.Chara uses Features.Story, so a change to Features.Story can break Features.Chara, while a change to Features.Chara can't break Features.Story.
- 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.
19→30 Features.Chara uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Chara uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Chara uses Features.Shared, so a change to Features.Shared can break Features.Chara, while a change to Features.Chara can't break Features.Shared.
- 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.
19→36 Features.Chara uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Chara uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Chara.CharaController→DragaliaAPI.Features.Missions.IMissionProgressionServiceDragaliaAPI.Features.Chara.CharaService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Chara uses Features.Missions, so a change to Features.Missions can break Features.Chara, while a change to Features.Chara can't break Features.Missions.
- 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.
20→1 Features.Trade uses Infrastructure.Results✕
- Connections
- 3 pairs of types, where a type in Features.Trade uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Trade.AbilityCrestTradeController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Trade.EventTradeController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Trade.TreasureTradeController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Trade uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Trade, while a change to Features.Trade can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→2 Features.Trade uses Shared.Definitions.Enums✕
- Connections
- 5 pairs of types, where a type in Features.Trade uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Trade.ITradeRepository→DragaliaAPI.Shared.Definitions.Enums.TradeTypeDragaliaAPI.Features.Trade.ITradeService→DragaliaAPI.Shared.Definitions.Enums.TradeTypeDragaliaAPI.Features.Trade.Log→DragaliaAPI.Shared.Definitions.Enums.TradeTypeDragaliaAPI.Features.Trade.TradeRepository→DragaliaAPI.Shared.Definitions.Enums.TradeTypeDragaliaAPI.Features.Trade.TradeService→DragaliaAPI.Shared.Definitions.Enums.TradeType
- Direction
- Features.Trade uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Trade, while a change to Features.Trade can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→3 Features.Trade uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Trade uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Trade.TradeRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Trade uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Trade, while a change to Features.Trade can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→4 Features.Trade uses Database.Entities✕
- Connections
- 2 pairs of types, where a type in Features.Trade uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Trade.ITradeRepository→DragaliaAPI.Database.Entities.DbPlayerTradeDragaliaAPI.Features.Trade.TradeRepository→DragaliaAPI.Database.Entities.DbPlayerTrade
- Direction
- Features.Trade uses Database.Entities, so a change to Database.Entities can break Features.Trade, while a change to Features.Trade can't break Database.Entities.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→6 Features.Trade uses Infrastructure✕
- Connections
- 3 pairs of types, where a type in Features.Trade uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Trade.AbilityCrestTradeController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Trade.EventTradeController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Trade.TreasureTradeController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Trade uses Infrastructure, so a change to Infrastructure can break Features.Trade, while a change to Features.Trade can't break Infrastructure.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→8 Features.Trade uses Database✕
- Connections
- 1 pair of types, where a type in Features.Trade uses a type in Database.
- The types involved
DragaliaAPI.Features.Trade.TradeRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Trade uses Database, so a change to Database can break Features.Trade, while a change to Features.Trade can't break Database.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→11 Features.Trade uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Trade uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Trade.TradeService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Trade uses Features.Present, so a change to Features.Present can break Features.Trade, while a change to Features.Trade can't break Features.Present.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→16 Features.Trade uses Features.Shared.Reward✕
- Connections
- 3 pairs of types, where a type in Features.Trade uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Trade.AbilityCrestTradeController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Trade.EventTradeController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Trade.TradeService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Trade uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Trade, while a change to Features.Trade can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→18 Features.Trade uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Trade uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Trade.TradeService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Trade uses Features.Shop, so a change to Features.Shop can break Features.Trade, while a change to Features.Trade can't break Features.Shop.
- Position
- Below the diagonal: Features.Trade uses a module listed above it, which is the healthy direction.
20→29 Features.Trade uses Features.Dmode part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Trade uses a type in Features.Dmode.
- The types involved
DragaliaAPI.Features.Trade.TreasureTradeController→DragaliaAPI.Features.Dmode.IDmodeService
- Direction
- Features.Trade uses Features.Dmode, so a change to Features.Dmode can break Features.Trade, while a change to Features.Trade can't break Features.Dmode.
- 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.
20→30 Features.Trade uses Features.Shared part of a loop✕
- Connections
- 3 pairs of types, where a type in Features.Trade uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Trade.AbilityCrestTradeController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Trade.EventTradeController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Trade.TreasureTradeController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Trade uses Features.Shared, so a change to Features.Shared can break Features.Trade, while a change to Features.Trade can't break Features.Shared.
- 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.
20→36 Features.Trade uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Trade uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Trade.AbilityCrestTradeController→DragaliaAPI.Features.Missions.IMissionProgressionServiceDragaliaAPI.Features.Trade.TradeService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Trade uses Features.Missions, so a change to Features.Missions can break Features.Trade, while a change to Features.Trade can't break Features.Missions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 Features.Dungeon.Record uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Dungeon.Record uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→3 Features.Dungeon.Record uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordHelperService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Dungeon.Record uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→6 Features.Dungeon.Record uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Dungeon.Record uses Infrastructure, so a change to Infrastructure can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Infrastructure.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→8 Features.Dungeon.Record uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Record uses a type in Database.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordHelperService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Dungeon.Record uses Database, so a change to Database can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Database.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→9 Features.Dungeon.Record uses Models.Generated✕
- Connections
- 11 pairs of types, where a type in Features.Dungeon.Record uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordController→DragaliaAPI.Models.Generated.DungeonRecordRecordMultiRequestDragaliaAPI.Features.Dungeon.Record.DungeonRecordDamageService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Models.Generated.AtgenDropAllDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Models.Generated.IngameResultDataDragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.Record.IDungeonRecordDamageService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.Record.IDungeonRecordRewardService→DragaliaAPI.Models.Generated.AtgenDropAllDragaliaAPI.Features.Dungeon.Record.IDungeonRecordRewardService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.Record.IDungeonRecordService→DragaliaAPI.Models.Generated.IngameResultDataDragaliaAPI.Features.Dungeon.Record.IDungeonRecordService→DragaliaAPI.Models.Generated.PlayRecord
- Direction
- Features.Dungeon.Record uses Models.Generated, so a change to Models.Generated can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Models.Generated.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→10 Features.Dungeon.Record uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Database.Repositories.IQuestRepository
- Direction
- Features.Dungeon.Record uses Database.Repositories, so a change to Database.Repositories can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Database.Repositories.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→11 Features.Dungeon.Record uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Dungeon.Record uses Features.Present, so a change to Features.Present can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Present.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→12 Features.Dungeon.Record uses Features.CoOp✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.CoOp.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordHelperService→DragaliaAPI.Features.CoOp.IMatchingService
- Direction
- Features.Dungeon.Record uses Features.CoOp, so a change to Features.CoOp can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.CoOp.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→13 Features.Dungeon.Record uses Features.Friends✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Record uses a type in Features.Friends.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordHelperService→DragaliaAPI.Features.Friends.FriendServiceDragaliaAPI.Features.Dungeon.Record.DungeonRecordHelperService→DragaliaAPI.Features.Friends.IHelperService
- Direction
- Features.Dungeon.Record uses Features.Friends, so a change to Features.Friends can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Friends.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→14 Features.Dungeon.Record uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Dungeon.Record uses Features.Player, so a change to Features.Player can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Player.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→16 Features.Dungeon.Record uses Features.Shared.Reward✕
- Connections
- 3 pairs of types, where a type in Features.Dungeon.Record uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Dungeon.Record.Extensions→DragaliaAPI.Features.Shared.Reward.Entity
- Direction
- Features.Dungeon.Record uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→17 Features.Dungeon.Record uses Features.Quest✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Quest.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Quest.IQuestService
- Direction
- Features.Dungeon.Record uses Features.Quest, so a change to Features.Quest can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Quest.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→19 Features.Dungeon.Record uses Features.Chara✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Chara.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Chara.ICharaService
- Direction
- Features.Dungeon.Record uses Features.Chara, so a change to Features.Chara can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Chara.
- Position
- Below the diagonal: Features.Dungeon.Record uses a module listed above it, which is the healthy direction.
21→23 Features.Dungeon.Record uses Features.Dungeon part of a loop✕
- Connections
- 9 pairs of types, where a type in Features.Dungeon.Record uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordController→DragaliaAPI.Features.Dungeon.IDungeonServiceDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Dungeon.DungeonSessionDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Dungeon.EventDropServiceDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Dungeon.IQuestCompletionServiceDragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Dungeon.QuestMissionStatusDragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Dungeon.DungeonSessionDragaliaAPI.Features.Dungeon.Record.IDungeonRecordRewardService→DragaliaAPI.Features.Dungeon.DungeonSessionDragaliaAPI.Features.Dungeon.Record.IDungeonRecordRewardService→DragaliaAPI.Features.Dungeon.QuestMissionStatusDragaliaAPI.Features.Dungeon.Record.IDungeonRecordService→DragaliaAPI.Features.Dungeon.DungeonSession
- Direction
- Features.Dungeon.Record uses Features.Dungeon, so a change to Features.Dungeon can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Dungeon.
- 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→25 Features.Dungeon.Record uses Features.Tutorial part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordService→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.Dungeon.Record uses Features.Tutorial, so a change to Features.Tutorial can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Tutorial.
- 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→30 Features.Dungeon.Record uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Dungeon.Record uses Features.Shared, so a change to Features.Shared can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Shared.
- 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→36 Features.Dungeon.Record uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Record uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Dungeon.Record.DungeonRecordRewardService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Dungeon.Record uses Features.Missions, so a change to Features.Missions can break Features.Dungeon.Record, while a change to Features.Dungeon.Record can't break Features.Missions.
- 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→1 Features.Event uses Infrastructure.Results✕
- Connections
- 6 pairs of types, where a type in Features.Event uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Event.BuildEventController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Event.Clb01EventController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Event.CombatEventController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Event.EarnEventController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Event.MemoryEventController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Event uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Event, while a change to Features.Event can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→3 Features.Event uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Features.Event uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Event.EventService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Event uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Event, while a change to Features.Event can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→4 Features.Event uses Database.Entities✕
- Connections
- 10 pairs of types, where a type in Features.Event uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Database.Entities.DbPlayerEventDataDragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Database.Entities.DbPlayerEventItemDragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Database.Entities.DbPlayerEventPassiveDragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Database.Entities.DbPlayerEventRewardDragaliaAPI.Features.Event.EventService→DragaliaAPI.Database.Entities.DbPlayerEventDataDragaliaAPI.Features.Event.IEventRepository→DragaliaAPI.Database.Entities.DbPlayerEventDataDragaliaAPI.Features.Event.IEventRepository→DragaliaAPI.Database.Entities.DbPlayerEventItemDragaliaAPI.Features.Event.IEventRepository→DragaliaAPI.Database.Entities.DbPlayerEventPassiveDragaliaAPI.Features.Event.IEventRepository→DragaliaAPI.Database.Entities.DbPlayerEventRewardDragaliaAPI.Features.Event.IEventRewardList→DragaliaAPI.Database.Entities.DbPlayerEventReward
- Direction
- Features.Event uses Database.Entities, so a change to Database.Entities can break Features.Event, while a change to Features.Event can't break Database.Entities.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→5 Features.Event uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Event uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Event.EventValidationFilter→DragaliaAPI.Features.Shared.Options.EventOptions
- Direction
- Features.Event uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Event, while a change to Features.Event can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→6 Features.Event uses Infrastructure✕
- Connections
- 6 pairs of types, where a type in Features.Event uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Event.BuildEventController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Event.Clb01EventController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Event.CombatEventController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Event.EarnEventController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Event.MemoryEventController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Event uses Infrastructure, so a change to Infrastructure can break Features.Event, while a change to Features.Event can't break Infrastructure.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→7 Features.Event uses Shared.MasterAsset.Models✕
- Connections
- 1 pair of types, where a type in Features.Event uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Event.EventService→DragaliaAPI.Shared.MasterAsset.Models.QuestData
- Direction
- Features.Event uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Event, while a change to Features.Event can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→8 Features.Event uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Event uses a type in Database.
- The types involved
DragaliaAPI.Features.Event.EventRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Event.EventService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Event uses Database, so a change to Database can break Features.Event, while a change to Features.Event can't break Database.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→9 Features.Event uses Models.Generated✕
- Connections
- 3 pairs of types, where a type in Features.Event uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Models.Generated.RaidEventEntryRequestDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Models.Generated.RaidEventGetEventDataRequestDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Models.Generated.RaidEventReceiveRaidPointRewardRequest
- Direction
- Features.Event uses Models.Generated, so a change to Models.Generated can break Features.Event, while a change to Features.Event can't break Models.Generated.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→10 Features.Event uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Event uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Event.MemoryEventController→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Event uses Database.Repositories, so a change to Database.Repositories can break Features.Event, while a change to Features.Event can't break Database.Repositories.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→16 Features.Event uses Features.Shared.Reward✕
- Connections
- 7 pairs of types, where a type in Features.Event uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Event.BuildEventController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.Clb01EventController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.CombatEventController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.EarnEventController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.EventService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.MemoryEventController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Event uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Event, while a change to Features.Event can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→20 Features.Event uses Features.Trade✕
- Connections
- 4 pairs of types, where a type in Features.Event uses a type in Features.Trade.
- The types involved
DragaliaAPI.Features.Event.BuildEventController→DragaliaAPI.Features.Trade.ITradeServiceDragaliaAPI.Features.Event.CombatEventController→DragaliaAPI.Features.Trade.ITradeServiceDragaliaAPI.Features.Event.EarnEventController→DragaliaAPI.Features.Trade.ITradeServiceDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Features.Trade.ITradeService
- Direction
- Features.Event uses Features.Trade, so a change to Features.Trade can break Features.Event, while a change to Features.Event can't break Features.Trade.
- Position
- Below the diagonal: Features.Event uses a module listed above it, which is the healthy direction.
22→30 Features.Event uses Features.Shared part of a loop✕
- Connections
- 6 pairs of types, where a type in Features.Event uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Event.BuildEventController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Event.Clb01EventController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Event.CombatEventController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Event.EarnEventController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Event.MemoryEventController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Event.RaidEventController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Event uses Features.Shared, so a change to Features.Shared can break Features.Event, while a change to Features.Event can't break Features.Shared.
- 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→36 Features.Event uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Event uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Event.EventService→DragaliaAPI.Features.Missions.IMissionProgressionServiceDragaliaAPI.Features.Event.EventService→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Event uses Features.Missions, so a change to Features.Missions can break Features.Event, while a change to Features.Event can't break Features.Missions.
- 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→1 Features.Dungeon uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Dungeon uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Dungeon, while a change to Features.Dungeon can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→2 Features.Dungeon uses Shared.Definitions.Enums✕
- Connections
- 5 pairs of types, where a type in Features.Dungeon uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Dungeon.AbilityLogic→DragaliaAPI.Shared.Definitions.Enums.AbilityTypesDragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Dungeon.DungeonSession→DragaliaAPI.Shared.Definitions.Enums.VariationTypesDragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Shared.Definitions.Enums.QuestCompleteTypeDragaliaAPI.Features.Dungeon.QuestEnemyService→DragaliaAPI.Shared.Definitions.Enums.VariationTypes
- Direction
- Features.Dungeon uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Dungeon, while a change to Features.Dungeon can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→3 Features.Dungeon uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Dungeon.DungeonService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Dungeon uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Dungeon, while a change to Features.Dungeon can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→4 Features.Dungeon uses Database.Entities✕
- Connections
- 12 pairs of types, where a type in Features.Dungeon uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbTalismanDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbWeaponBodyDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbWeaponPassiveAbilityDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Database.Entities.DbWeaponSkinDragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Database.Entities.DbQuestClearPartyUnitDragaliaAPI.Features.Dungeon.IDungeonRepository→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Dungeon.IDungeonRepository→DragaliaAPI.Database.Entities.DbQuestClearPartyUnit
- Direction
- Features.Dungeon uses Database.Entities, so a change to Database.Entities can break Features.Dungeon, while a change to Features.Dungeon can't break Database.Entities.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→5 Features.Dungeon uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonService→DragaliaAPI.Features.Shared.Options.RedisCachingOptions
- Direction
- Features.Dungeon uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→6 Features.Dungeon uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Dungeon.DungeonException→DragaliaAPI.Infrastructure.DragaliaException
- Direction
- Features.Dungeon uses Infrastructure, so a change to Infrastructure can break Features.Dungeon, while a change to Features.Dungeon can't break Infrastructure.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→7 Features.Dungeon uses Shared.MasterAsset.Models✕
- Connections
- 4 pairs of types, where a type in Features.Dungeon uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Dungeon.AbilityLogic→DragaliaAPI.Shared.MasterAsset.Models.AbilityDataDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Shared.MasterAsset.Models.AreaInfoDragaliaAPI.Features.Dungeon.DungeonSession→DragaliaAPI.Shared.MasterAsset.Models.QuestDataDragaliaAPI.Features.Dungeon.EventDropService→DragaliaAPI.Shared.MasterAsset.Models.QuestData
- Direction
- Features.Dungeon uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Dungeon, while a change to Features.Dungeon can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→8 Features.Dungeon uses Database✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Database.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Dungeon uses Database, so a change to Database can break Features.Dungeon, while a change to Features.Dungeon can't break Database.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→9 Features.Dungeon uses Models.Generated✕
- Connections
- 15 pairs of types, where a type in Features.Dungeon uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Models.Generated.DragonListDragaliaAPI.Features.Dungeon.DungeonMapper→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.DungeonRepository→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.DungeonSession→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.Extensions→DragaliaAPI.Models.Generated.AtgenDropAllDragaliaAPI.Features.Dungeon.Extensions→DragaliaAPI.Models.Generated.IngameResultDataDragaliaAPI.Features.Dungeon.Extensions→DragaliaAPI.Models.Generated.UpdateDataListDragaliaAPI.Features.Dungeon.IDungeonRepository→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.IDungeonStartService→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.IOddsInfoService→DragaliaAPI.Models.Generated.OddsInfoDragaliaAPI.Features.Dungeon.IQuestCompletionService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.OddsInfoService→DragaliaAPI.Models.Generated.OddsInfoDragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Models.Generated.PlayRecordDragaliaAPI.Features.Dungeon.StubData→DragaliaAPI.Models.Generated.OddsInfo
- Direction
- Features.Dungeon uses Models.Generated, so a change to Models.Generated can break Features.Dungeon, while a change to Features.Dungeon can't break Models.Generated.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→10 Features.Dungeon uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Database.Repositories.IUnitRepository
- Direction
- Features.Dungeon uses Database.Repositories, so a change to Database.Repositories can break Features.Dungeon, while a change to Features.Dungeon can't break Database.Repositories.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→12 Features.Dungeon uses Features.CoOp✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.CoOp.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Features.CoOp.IMatchingService
- Direction
- Features.Dungeon uses Features.CoOp, so a change to Features.CoOp can break Features.Dungeon, while a change to Features.Dungeon can't break Features.CoOp.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→14 Features.Dungeon uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Dungeon.IDungeonStartService→DragaliaAPI.Features.Player.StaminaType
- Direction
- Features.Dungeon uses Features.Player, so a change to Features.Player can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Player.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→16 Features.Dungeon uses Features.Shared.Reward✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Dungeon uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→17 Features.Dungeon uses Features.Quest✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Quest.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Features.Quest.IQuestService
- Direction
- Features.Dungeon uses Features.Quest, so a change to Features.Quest can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Quest.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→21 Features.Dungeon uses Features.Dungeon.Record✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Dungeon.Record.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Features.Dungeon.Record.IDungeonRecordHelperService
- Direction
- Features.Dungeon uses Features.Dungeon.Record, so a change to Features.Dungeon.Record can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Dungeon.Record.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→22 Features.Dungeon uses Features.Event✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Dungeon.EventDropService→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Dungeon uses Features.Event, so a change to Features.Event can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Event.
- Position
- Below the diagonal: Features.Dungeon uses a module listed above it, which is the healthy direction.
23→30 Features.Dungeon uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Dungeon.DungeonController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Dungeon uses Features.Shared, so a change to Features.Shared can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Shared.
- 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→36 Features.Dungeon uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Dungeon.QuestCompletionService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Dungeon uses Features.Missions, so a change to Features.Missions can break Features.Dungeon, while a change to Features.Dungeon can't break Features.Missions.
- 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→1 Features.Wall uses Infrastructure.Results✕
- Connections
- 3 pairs of types, where a type in Features.Wall uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Wall.WallController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Wall.WallStartController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Wall uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Wall, while a change to Features.Wall can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→2 Features.Wall uses Shared.Definitions.Enums✕
- Connections
- 2 pairs of types, where a type in Features.Wall uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Wall.IWallService→DragaliaAPI.Shared.Definitions.Enums.QuestWallTypesDragaliaAPI.Features.Wall.WallService→DragaliaAPI.Shared.Definitions.Enums.QuestWallTypes
- Direction
- Features.Wall uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Wall, while a change to Features.Wall can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→3 Features.Wall uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Wall uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Wall.WallService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Wall uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Wall, while a change to Features.Wall can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→4 Features.Wall uses Database.Entities✕
- Connections
- 4 pairs of types, where a type in Features.Wall uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Wall.IWallService→DragaliaAPI.Database.Entities.DbPlayerQuestWallDragaliaAPI.Features.Wall.IWallService→DragaliaAPI.Database.Entities.DbWallRewardDateDragaliaAPI.Features.Wall.WallService→DragaliaAPI.Database.Entities.DbPlayerQuestWallDragaliaAPI.Features.Wall.WallService→DragaliaAPI.Database.Entities.DbWallRewardDate
- Direction
- Features.Wall uses Database.Entities, so a change to Database.Entities can break Features.Wall, while a change to Features.Wall can't break Database.Entities.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→6 Features.Wall uses Infrastructure✕
- Connections
- 3 pairs of types, where a type in Features.Wall uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Wall.WallController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Wall.WallStartController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Wall uses Infrastructure, so a change to Infrastructure can break Features.Wall, while a change to Features.Wall can't break Infrastructure.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→8 Features.Wall uses Database✕
- Connections
- 1 pair of types, where a type in Features.Wall uses a type in Database.
- The types involved
DragaliaAPI.Features.Wall.WallService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Wall uses Database, so a change to Database can break Features.Wall, while a change to Features.Wall can't break Database.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→11 Features.Wall uses Features.Present✕
- Connections
- 2 pairs of types, where a type in Features.Wall uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Present.IPresentServiceDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Present.Present
- Direction
- Features.Wall uses Features.Present, so a change to Features.Present can break Features.Wall, while a change to Features.Wall can't break Features.Present.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→16 Features.Wall uses Features.Shared.Reward✕
- Connections
- 4 pairs of types, where a type in Features.Wall uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Wall.WallController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Shared.Reward.EntityDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Wall.WallService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Wall uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Wall, while a change to Features.Wall can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→21 Features.Wall uses Features.Dungeon.Record✕
- Connections
- 1 pair of types, where a type in Features.Wall uses a type in Features.Dungeon.Record.
- The types involved
DragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Dungeon.Record.IDungeonRecordHelperService
- Direction
- Features.Wall uses Features.Dungeon.Record, so a change to Features.Dungeon.Record can break Features.Wall, while a change to Features.Wall can't break Features.Dungeon.Record.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→23 Features.Wall uses Features.Dungeon✕
- Connections
- 4 pairs of types, where a type in Features.Wall uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.Wall.WallController→DragaliaAPI.Features.Dungeon.IDungeonServiceDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Dungeon.IDungeonServiceDragaliaAPI.Features.Wall.WallStartController→DragaliaAPI.Features.Dungeon.IDungeonStartServiceDragaliaAPI.Features.Wall.WallStartController→DragaliaAPI.Features.Dungeon.IOddsInfoService
- Direction
- Features.Wall uses Features.Dungeon, so a change to Features.Dungeon can break Features.Wall, while a change to Features.Wall can't break Features.Dungeon.
- Position
- Below the diagonal: Features.Wall uses a module listed above it, which is the healthy direction.
24→30 Features.Wall uses Features.Shared part of a loop✕
- Connections
- 3 pairs of types, where a type in Features.Wall uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Wall.WallController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Wall.WallRecordController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Wall.WallStartController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Wall uses Features.Shared, so a change to Features.Shared can break Features.Wall, while a change to Features.Wall can't break Features.Shared.
- 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→36 Features.Wall uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Wall uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Wall.WallService→DragaliaAPI.Features.Missions.IMissionProgressionServiceDragaliaAPI.Features.Wall.WallService→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Wall uses Features.Missions, so a change to Features.Missions can break Features.Wall, while a change to Features.Wall can't break Features.Missions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 Features.Tutorial uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Tutorial uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Tutorial, while a change to Features.Tutorial can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Tutorial uses a module listed above it, which is the healthy direction.
25→6 Features.Tutorial uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Tutorial uses Infrastructure, so a change to Infrastructure can break Features.Tutorial, while a change to Features.Tutorial can't break Infrastructure.
- Position
- Below the diagonal: Features.Tutorial uses a module listed above it, which is the healthy direction.
25→10 Features.Tutorial uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Tutorial uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Tutorial.TutorialService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Tutorial uses Database.Repositories, so a change to Database.Repositories can break Features.Tutorial, while a change to Features.Tutorial can't break Database.Repositories.
- Position
- Below the diagonal: Features.Tutorial uses a module listed above it, which is the healthy direction.
25→24 Features.Tutorial uses Features.Wall✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Features.Wall.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialService→DragaliaAPI.Features.Wall.IWallService
- Direction
- Features.Tutorial uses Features.Wall, so a change to Features.Wall can break Features.Tutorial, while a change to Features.Tutorial can't break Features.Wall.
- Position
- Below the diagonal: Features.Tutorial uses a module listed above it, which is the healthy direction.
25→30 Features.Tutorial uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Tutorial uses Features.Shared, so a change to Features.Shared can break Features.Tutorial, while a change to Features.Tutorial can't break Features.Shared.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 Features.Tutorial uses Features.Fort part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialService→DragaliaAPI.Features.Fort.IFortRepository
- Direction
- Features.Tutorial uses Features.Fort, so a change to Features.Fort can break Features.Tutorial, while a change to Features.Tutorial can't break Features.Fort.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→37 Features.Tutorial uses Features.AbilityCrests part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Tutorial uses a type in Features.AbilityCrests.
- The types involved
DragaliaAPI.Features.Tutorial.TutorialService→DragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository
- Direction
- Features.Tutorial uses Features.AbilityCrests, so a change to Features.AbilityCrests can break Features.Tutorial, while a change to Features.Tutorial can't break Features.AbilityCrests.
- 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.
26→1 Features.Story uses Infrastructure.Results✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Story.CastleStoryController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Story.StoryController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Story uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Story, while a change to Features.Story can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→2 Features.Story uses Shared.Definitions.Enums✕
- Connections
- 4 pairs of types, where a type in Features.Story uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Story.IStoryRepository→DragaliaAPI.Shared.Definitions.Enums.StoryTypesDragaliaAPI.Features.Story.IStoryService→DragaliaAPI.Shared.Definitions.Enums.StoryTypesDragaliaAPI.Features.Story.StoryRepository→DragaliaAPI.Shared.Definitions.Enums.StoryTypesDragaliaAPI.Features.Story.StoryService→DragaliaAPI.Shared.Definitions.Enums.StoryTypes
- Direction
- Features.Story uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Story, while a change to Features.Story can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→3 Features.Story uses Shared.PlayerDetails✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Story.StoryRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Story.StoryService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Story uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Story, while a change to Features.Story can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→4 Features.Story uses Database.Entities✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Story.IStoryRepository→DragaliaAPI.Database.Entities.DbPlayerStoryStateDragaliaAPI.Features.Story.StoryRepository→DragaliaAPI.Database.Entities.DbPlayerStoryState
- Direction
- Features.Story uses Database.Entities, so a change to Database.Entities can break Features.Story, while a change to Features.Story can't break Database.Entities.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→6 Features.Story uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Story.CastleStoryController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Story.StoryController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Story uses Infrastructure, so a change to Infrastructure can break Features.Story, while a change to Features.Story can't break Infrastructure.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→8 Features.Story uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Database.
- The types involved
DragaliaAPI.Features.Story.StoryRepository→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Story.StoryService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Story uses Database, so a change to Database can break Features.Story, while a change to Features.Story can't break Database.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→10 Features.Story uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Story.StoryService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Story uses Database.Repositories, so a change to Database.Repositories can break Features.Story, while a change to Features.Story can't break Database.Repositories.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→11 Features.Story uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Story uses Features.Present, so a change to Features.Present can break Features.Story, while a change to Features.Story can't break Features.Present.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→14 Features.Story uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Story uses Features.Player, so a change to Features.Player can break Features.Story, while a change to Features.Story can't break Features.Player.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→16 Features.Story uses Features.Shared.Reward✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Story uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Story, while a change to Features.Story can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→18 Features.Story uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Story uses Features.Shop, so a change to Features.Shop can break Features.Story, while a change to Features.Story can't break Features.Shop.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→25 Features.Story uses Features.Tutorial✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.Story uses Features.Tutorial, so a change to Features.Tutorial can break Features.Story, while a change to Features.Story can't break Features.Tutorial.
- Position
- Below the diagonal: Features.Story uses a module listed above it, which is the healthy direction.
26→30 Features.Story uses Features.Shared part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Story uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Story.CastleStoryController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Story.StoryController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Story uses Features.Shared, so a change to Features.Shared can break Features.Story, while a change to Features.Story can't break Features.Shared.
- 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.
26→32 Features.Story uses Features.Fort part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Fort.IFortRepository
- Direction
- Features.Story uses Features.Fort, so a change to Features.Fort can break Features.Story, while a change to Features.Story can't break Features.Fort.
- 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.
26→36 Features.Story uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Story uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Story.StoryService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Story uses Features.Missions, so a change to Features.Missions can break Features.Story, while a change to Features.Story can't break Features.Missions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 Features.Summoning uses Infrastructure.Results✕
- Connections
- 2 pairs of types, where a type in Features.Summoning uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Summoning.RedoableSummonController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Summoning.SummonController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Summoning uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Summoning, while a change to Features.Summoning can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→2 Features.Summoning uses Shared.Definitions.Enums✕
- Connections
- 8 pairs of types, where a type in Features.Summoning uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Summoning.Banner→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Summoning.Banner→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Summoning.SummonRequestInfo→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Summoning.UnitRate→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Summoning.UnitRate→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Summoning.UnitRate→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Summoning.UnitService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Summoning.UnitService→DragaliaAPI.Shared.Definitions.Enums.DragonId
- Direction
- Features.Summoning uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Summoning, while a change to Features.Summoning can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→3 Features.Summoning uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Summoning uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Summoning uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Summoning, while a change to Features.Summoning can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→4 Features.Summoning uses Database.Entities✕
- Connections
- 1 pair of types, where a type in Features.Summoning uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Database.Entities.DbPlayerBannerData
- Direction
- Features.Summoning uses Database.Entities, so a change to Database.Entities can break Features.Summoning, while a change to Features.Summoning can't break Database.Entities.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→6 Features.Summoning uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Features.Summoning uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Summoning.RedoableSummonController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Summoning.SummonController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Summoning uses Infrastructure, so a change to Infrastructure can break Features.Summoning, while a change to Features.Summoning can't break Infrastructure.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→7 Features.Summoning uses Shared.MasterAsset.Models✕
- Connections
- 5 pairs of types, where a type in Features.Summoning uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Summoning.Banner→DragaliaAPI.Shared.MasterAsset.Models.CharaDataDragaliaAPI.Features.Summoning.Banner→DragaliaAPI.Shared.MasterAsset.Models.DragonDataDragaliaAPI.Features.Summoning.SummonOddsLogic→DragaliaAPI.Shared.MasterAsset.Models.CharaDataDragaliaAPI.Features.Summoning.SummonOddsLogic→DragaliaAPI.Shared.MasterAsset.Models.DragonDataDragaliaAPI.Features.Summoning.SummonOddsLogic→DragaliaAPI.Shared.MasterAsset.Models.IUnitData
- Direction
- Features.Summoning uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Summoning, while a change to Features.Summoning can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→8 Features.Summoning uses Database✕
- Connections
- 3 pairs of types, where a type in Features.Summoning uses a type in Database.
- The types involved
DragaliaAPI.Features.Summoning.SummonOddsService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Summoning.UnitService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Summoning uses Database, so a change to Database can break Features.Summoning, while a change to Features.Summoning can't break Database.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→11 Features.Summoning uses Features.Present✕
- Connections
- 2 pairs of types, where a type in Features.Summoning uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Features.Present.IPresentServiceDragaliaAPI.Features.Summoning.UnitService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Summoning uses Features.Present, so a change to Features.Present can break Features.Summoning, while a change to Features.Summoning can't break Features.Present.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→16 Features.Summoning uses Features.Shared.Reward✕
- Connections
- 3 pairs of types, where a type in Features.Summoning uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Summoning.Log→DragaliaAPI.Features.Shared.Reward.RewardGrantResultDragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Summoning.UnitService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Summoning uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Summoning, while a change to Features.Summoning can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→18 Features.Summoning uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Summoning uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Summoning.SummonService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Summoning uses Features.Shop, so a change to Features.Shop can break Features.Summoning, while a change to Features.Summoning can't break Features.Shop.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→25 Features.Summoning uses Features.Tutorial✕
- Connections
- 1 pair of types, where a type in Features.Summoning uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.Summoning.RedoableSummonController→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.Summoning uses Features.Tutorial, so a change to Features.Tutorial can break Features.Summoning, while a change to Features.Summoning can't break Features.Tutorial.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→26 Features.Summoning uses Features.Story✕
- Connections
- 1 pair of types, where a type in Features.Summoning uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Summoning.RedoableSummonController→DragaliaAPI.Features.Story.IStoryRepository
- Direction
- Features.Summoning uses Features.Story, so a change to Features.Story can break Features.Summoning, while a change to Features.Summoning can't break Features.Story.
- Position
- Below the diagonal: Features.Summoning uses a module listed above it, which is the healthy direction.
27→30 Features.Summoning uses Features.Shared part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Summoning uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Summoning.RedoableSummonController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Summoning.SummonController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Summoning uses Features.Shared, so a change to Features.Shared can break Features.Summoning, while a change to Features.Summoning can't break Features.Shared.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 Features.Login.Actions uses Shared.Definitions.Enums✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Login.Actions.DragonGiftResetAction→DragaliaAPI.Shared.Definitions.Enums.DragonGifts
- Direction
- Features.Login.Actions uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Login.Actions, while a change to Features.Login.Actions can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→3 Features.Login.Actions uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Login.Actions.DragonGiftResetAction→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Login.Actions uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Login.Actions, while a change to Features.Login.Actions can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→5 Features.Login.Actions uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Login.Actions.DailyEndeavourResetAction→DragaliaAPI.Features.Shared.Options.EventOptions
- Direction
- Features.Login.Actions uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→8 Features.Login.Actions uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Login.Actions uses a type in Database.
- The types involved
DragaliaAPI.Features.Login.Actions.DailySummoningDealResetAction→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.Actions.DragonGiftResetAction→DragaliaAPI.Database.ApiContext
- Direction
- Features.Login.Actions uses Database, so a change to Database can break Features.Login.Actions, while a change to Features.Login.Actions can't break Database.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→11 Features.Login.Actions uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Login.Actions.LoginGiftResetAction→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Login.Actions uses Features.Present, so a change to Features.Present can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Present.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→18 Features.Login.Actions uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Login.Actions.ItemSummonResetAction→DragaliaAPI.Features.Shop.IShopRepository
- Direction
- Features.Login.Actions uses Features.Shop, so a change to Features.Shop can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Shop.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→22 Features.Login.Actions uses Features.Event✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Login.Actions.DailyEndeavourResetAction→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Login.Actions uses Features.Event, so a change to Features.Event can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Event.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→27 Features.Login.Actions uses Features.Summoning✕
- Connections
- 1 pair of types, where a type in Features.Login.Actions uses a type in Features.Summoning.
- The types involved
DragaliaAPI.Features.Login.Actions.DailySummoningDealResetAction→DragaliaAPI.Features.Summoning.SummonBannerOptions
- Direction
- Features.Login.Actions uses Features.Summoning, so a change to Features.Summoning can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Summoning.
- Position
- Below the diagonal: Features.Login.Actions uses a module listed above it, which is the healthy direction.
28→36 Features.Login.Actions uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Login.Actions uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Login.Actions.DailyEndeavourResetAction→DragaliaAPI.Features.Missions.IMissionRepositoryDragaliaAPI.Features.Login.Actions.DailyEndeavourResetAction→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Login.Actions uses Features.Missions, so a change to Features.Missions can break Features.Login.Actions, while a change to Features.Login.Actions can't break Features.Missions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 Features.Dmode uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Dmode uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Dmode, while a change to Features.Dmode can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→2 Features.Dmode uses Shared.Definitions.Enums✕
- Connections
- 7 pairs of types, where a type in Features.Dmode uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Shared.Definitions.Enums.DmodeServitorPassiveTypeDragaliaAPI.Features.Dmode.DmodeService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Shared.Definitions.Enums.DmodeServitorPassiveTypeDragaliaAPI.Features.Dmode.IDmodeService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Dmode.Log→DragaliaAPI.Shared.Definitions.Enums.Charas
- Direction
- Features.Dmode uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Dmode, while a change to Features.Dmode can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→3 Features.Dmode uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Dmode uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Dmode, while a change to Features.Dmode can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→4 Features.Dmode uses Database.Entities✕
- Connections
- 10 pairs of types, where a type in Features.Dmode uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeCharaDragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeDungeonDragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeExpeditionDragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeInfoDragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeServitorPassiveDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeCharaDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeDungeonDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeExpeditionDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeInfoDragaliaAPI.Features.Dmode.IDmodeRepository→DragaliaAPI.Database.Entities.DbPlayerDmodeServitorPassive
- Direction
- Features.Dmode uses Database.Entities, so a change to Database.Entities can break Features.Dmode, while a change to Features.Dmode can't break Database.Entities.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→6 Features.Dmode uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Features.Dmode uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Dmode.Log→DragaliaAPI.Infrastructure.DragaliaException
- Direction
- Features.Dmode uses Infrastructure, so a change to Infrastructure can break Features.Dmode, while a change to Features.Dmode can't break Infrastructure.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→8 Features.Dmode uses Database✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Database.
- The types involved
DragaliaAPI.Features.Dmode.DmodeRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Dmode uses Database, so a change to Database can break Features.Dmode, while a change to Features.Dmode can't break Database.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→16 Features.Dmode uses Features.Shared.Reward✕
- Connections
- 2 pairs of types, where a type in Features.Dmode uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Dmode.DmodeService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Dmode uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Dmode, while a change to Features.Dmode can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→18 Features.Dmode uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Dmode.DmodeService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Dmode uses Features.Shop, so a change to Features.Shop can break Features.Dmode, while a change to Features.Dmode can't break Features.Shop.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→26 Features.Dmode uses Features.Story✕
- Connections
- 2 pairs of types, where a type in Features.Dmode uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Features.Story.IStoryService
- Direction
- Features.Dmode uses Features.Story, so a change to Features.Story can break Features.Dmode, while a change to Features.Dmode can't break Features.Story.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→28 Features.Dmode uses Features.Login.Actions✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Features.Login.Actions.
- The types involved
DragaliaAPI.Features.Dmode.DmodeSkipResetAction→DragaliaAPI.Features.Login.Actions.IDailyResetAction
- Direction
- Features.Dmode uses Features.Login.Actions, so a change to Features.Login.Actions can break Features.Dmode, while a change to Features.Dmode can't break Features.Login.Actions.
- Position
- Below the diagonal: Features.Dmode uses a module listed above it, which is the healthy direction.
29→30 Features.Dmode uses Features.Shared part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dmode uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Dmode.DmodeController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Dmode uses Features.Shared, so a change to Features.Shared can break Features.Dmode, while a change to Features.Dmode can't break Features.Shared.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→3 Features.Shared uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Shared uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Shared, while a change to Features.Shared can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→8 Features.Shared uses Database✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Database.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Shared uses Database, so a change to Database can break Features.Shared, while a change to Features.Shared can't break Database.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→9 Features.Shared uses Models.Generated✕
- Connections
- 4 pairs of types, where a type in Features.Shared uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Shared.BaasApi→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Shared.IBaasApi→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Shared.IUpdateDataService→DragaliaAPI.Models.Generated.UpdateDataListDragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Models.Generated.UpdateDataList
- Direction
- Features.Shared uses Models.Generated, so a change to Models.Generated can break Features.Shared, while a change to Features.Shared can't break Models.Generated.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→11 Features.Shared uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Shared uses Features.Present, so a change to Features.Present can break Features.Shared, while a change to Features.Shared can't break Features.Present.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→13 Features.Shared uses Features.Friends✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Features.Friends.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Friends.IFriendNotificationService
- Direction
- Features.Shared uses Features.Friends, so a change to Features.Friends can break Features.Shared, while a change to Features.Shared can't break Features.Friends.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→22 Features.Shared uses Features.Event✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Event.IEventService
- Direction
- Features.Shared uses Features.Event, so a change to Features.Event can break Features.Shared, while a change to Features.Shared can't break Features.Event.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→29 Features.Shared uses Features.Dmode✕
- Connections
- 1 pair of types, where a type in Features.Shared uses a type in Features.Dmode.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Dmode.IDmodeService
- Direction
- Features.Shared uses Features.Dmode, so a change to Features.Dmode can break Features.Shared, while a change to Features.Shared can't break Features.Dmode.
- Position
- Below the diagonal: Features.Shared uses a module listed above it, which is the healthy direction.
30→36 Features.Shared uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Shared uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Missions.IMissionProgressionServiceDragaliaAPI.Features.Shared.UpdateDataService→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Shared uses Features.Missions, so a change to Features.Missions can break Features.Shared, while a change to Features.Shared can't break Features.Missions.
- 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.
31→1 Features.Dragons uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Dragons.DragonController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Dragons uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Dragons, while a change to Features.Dragons can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→2 Features.Dragons uses Shared.Definitions.Enums✕
- Connections
- 4 pairs of types, where a type in Features.Dragons uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Shared.Definitions.Enums.DragonGiftsDragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Features.Dragons.Log→DragaliaAPI.Shared.Definitions.Enums.DragonGifts
- Direction
- Features.Dragons uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Dragons, while a change to Features.Dragons can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→4 Features.Dragons uses Database.Entities✕
- Connections
- 3 pairs of types, where a type in Features.Dragons uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.Entities.DbPlayerDragonReliabilityDragaliaAPI.Features.Dragons.Log→DragaliaAPI.Database.Entities.DbPlayerDragonData
- Direction
- Features.Dragons uses Database.Entities, so a change to Database.Entities can break Features.Dragons, while a change to Features.Dragons can't break Database.Entities.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→6 Features.Dragons uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Dragons.DragonController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Dragons uses Infrastructure, so a change to Infrastructure can break Features.Dragons, while a change to Features.Dragons can't break Infrastructure.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→8 Features.Dragons uses Database✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Database.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Dragons uses Database, so a change to Database can break Features.Dragons, while a change to Features.Dragons can't break Database.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→10 Features.Dragons uses Database.Repositories✕
- Connections
- 3 pairs of types, where a type in Features.Dragons uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.Repositories.IUnitRepositoryDragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Dragons uses Database.Repositories, so a change to Database.Repositories can break Features.Dragons, while a change to Features.Dragons can't break Database.Repositories.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→16 Features.Dragons uses Features.Shared.Reward✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Dragons uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Dragons, while a change to Features.Dragons can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→18 Features.Dragons uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Dragons uses Features.Shop, so a change to Features.Shop can break Features.Dragons, while a change to Features.Dragons can't break Features.Shop.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→26 Features.Dragons uses Features.Story✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Features.Story.IStoryRepository
- Direction
- Features.Dragons uses Features.Story, so a change to Features.Story can break Features.Dragons, while a change to Features.Dragons can't break Features.Story.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→30 Features.Dragons uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Dragons uses Features.Shared, so a change to Features.Shared can break Features.Dragons, while a change to Features.Dragons can't break Features.Shared.
- Position
- Below the diagonal: Features.Dragons uses a module listed above it, which is the healthy direction.
31→36 Features.Dragons uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Dragons uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Dragons.DragonService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Dragons uses Features.Missions, so a change to Features.Missions can break Features.Dragons, while a change to Features.Dragons can't break Features.Missions.
- 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.
32→1 Features.Fort uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Fort.FortController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Fort uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Fort, while a change to Features.Fort can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→2 Features.Fort uses Shared.Definitions.Enums✕
- Connections
- 8 pairs of types, where a type in Features.Fort uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Fort.BonusService→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Features.Fort.FortRepository→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Fort.IFortRepository→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Fort.IFortService→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Fort.IFortService→DragaliaAPI.Shared.Definitions.Enums.PaymentTypesDragaliaAPI.Features.Fort.Log→DragaliaAPI.Shared.Definitions.Enums.FortPlants
- Direction
- Features.Fort uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Fort, while a change to Features.Fort can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→3 Features.Fort uses Shared.PlayerDetails✕
- Connections
- 3 pairs of types, where a type in Features.Fort uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Fort.BonusService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Fort.FortRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Fort uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Fort, while a change to Features.Fort can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→4 Features.Fort uses Database.Entities✕
- Connections
- 6 pairs of types, where a type in Features.Fort uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Fort.FortRepository→DragaliaAPI.Database.Entities.DbFortBuildDragaliaAPI.Features.Fort.FortRepository→DragaliaAPI.Database.Entities.DbFortDetailDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Database.Entities.DbFortBuildDragaliaAPI.Features.Fort.IFortRepository→DragaliaAPI.Database.Entities.DbFortBuildDragaliaAPI.Features.Fort.IFortRepository→DragaliaAPI.Database.Entities.DbFortDetailDragaliaAPI.Features.Fort.IFortService→DragaliaAPI.Database.Entities.DbFortBuild
- Direction
- Features.Fort uses Database.Entities, so a change to Database.Entities can break Features.Fort, while a change to Features.Fort can't break Database.Entities.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→5 Features.Fort uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Fort.FortService→DragaliaAPI.Features.Shared.Options.DragonfruitConfig
- Direction
- Features.Fort uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Fort, while a change to Features.Fort can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→6 Features.Fort uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Fort.FortController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Fort uses Infrastructure, so a change to Infrastructure can break Features.Fort, while a change to Features.Fort can't break Infrastructure.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→7 Features.Fort uses Shared.MasterAsset.Models✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Fort.FortService→DragaliaAPI.Shared.MasterAsset.Models.FortPlantDetail
- Direction
- Features.Fort uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Fort, while a change to Features.Fort can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→8 Features.Fort uses Database✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Database.
- The types involved
DragaliaAPI.Features.Fort.FortRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Fort uses Database, so a change to Database can break Features.Fort, while a change to Features.Fort can't break Database.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→10 Features.Fort uses Database.Repositories✕
- Connections
- 3 pairs of types, where a type in Features.Fort uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Fort.BonusService→DragaliaAPI.Database.Repositories.IWeaponRepositoryDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Fort uses Database.Repositories, so a change to Database.Repositories can break Features.Fort, while a change to Features.Fort can't break Database.Repositories.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→14 Features.Fort uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Fort.FortService→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Fort uses Features.Player, so a change to Features.Player can break Features.Fort, while a change to Features.Fort can't break Features.Player.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→16 Features.Fort uses Features.Shared.Reward✕
- Connections
- 2 pairs of types, where a type in Features.Fort uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Fort.FortController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Fort.FortService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Fort uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Fort, while a change to Features.Fort can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→18 Features.Fort uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Fort.FortService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Fort uses Features.Shop, so a change to Features.Shop can break Features.Fort, while a change to Features.Fort can't break Features.Shop.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→30 Features.Fort uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Fort.FortController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Fort uses Features.Shared, so a change to Features.Shared can break Features.Fort, while a change to Features.Fort can't break Features.Shared.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→31 Features.Fort uses Features.Dragons✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Dragons.
- The types involved
DragaliaAPI.Features.Fort.FortController→DragaliaAPI.Features.Dragons.IDragonService
- Direction
- Features.Fort uses Features.Dragons, so a change to Features.Dragons can break Features.Fort, while a change to Features.Fort can't break Features.Dragons.
- Position
- Below the diagonal: Features.Fort uses a module listed above it, which is the healthy direction.
32→36 Features.Fort uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Fort uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Fort.FortService→DragaliaAPI.Features.Missions.IFortMissionProgressionService
- Direction
- Features.Fort uses Features.Missions, so a change to Features.Missions can break Features.Fort, while a change to Features.Fort can't break Features.Missions.
- 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.
33→1 Features.Dungeon.Start uses Infrastructure.Results✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Start uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Infrastructure.Results.ResultCode
- Direction
- Features.Dungeon.Start uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→3 Features.Dungeon.Start uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Dungeon.Start uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→4 Features.Dungeon.Start uses Database.Entities✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Database.Entities.DbPartyUnit
- Direction
- Features.Dungeon.Start uses Database.Entities, so a change to Database.Entities can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Database.Entities.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→6 Features.Dungeon.Start uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Dungeon.Start uses Infrastructure, so a change to Infrastructure can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Infrastructure.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→7 Features.Dungeon.Start uses Shared.MasterAsset.Models✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Start uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Dungeon.Start.QuestOrderPartyMapper→DragaliaAPI.Shared.MasterAsset.Models.CharaDataDragaliaAPI.Features.Dungeon.Start.QuestOrderPartyMapper→DragaliaAPI.Shared.MasterAsset.Models.QuestOrderParty
- Direction
- Features.Dungeon.Start uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→8 Features.Dungeon.Start uses Database✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Database.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Dungeon.Start uses Database, so a change to Database can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Database.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→9 Features.Dungeon.Start uses Models.Generated✕
- Connections
- 4 pairs of types, where a type in Features.Dungeon.Start uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartMapper→DragaliaAPI.Models.Generated.DragonListDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Dungeon.Start.QuestOrderPartyMapper→DragaliaAPI.Models.Generated.DragonListDragaliaAPI.Features.Dungeon.Start.QuestOrderPartyMapper→DragaliaAPI.Models.Generated.PartySettingList
- Direction
- Features.Dungeon.Start uses Models.Generated, so a change to Models.Generated can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Models.Generated.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→10 Features.Dungeon.Start uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Start uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Database.Repositories.IWeaponRepository
- Direction
- Features.Dungeon.Start uses Database.Repositories, so a change to Database.Repositories can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Database.Repositories.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→12 Features.Dungeon.Start uses Features.CoOp✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.CoOp.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Features.CoOp.IMatchingService
- Direction
- Features.Dungeon.Start uses Features.CoOp, so a change to Features.CoOp can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.CoOp.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→13 Features.Dungeon.Start uses Features.Friends✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Friends.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Friends.IHelperService
- Direction
- Features.Dungeon.Start uses Features.Friends, so a change to Features.Friends can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Friends.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→14 Features.Dungeon.Start uses Features.Player✕
- Connections
- 2 pairs of types, where a type in Features.Dungeon.Start uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Player.IUserServiceDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Player.StaminaType
- Direction
- Features.Dungeon.Start uses Features.Player, so a change to Features.Player can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Player.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→17 Features.Dungeon.Start uses Features.Quest✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Quest.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Quest.IQuestService
- Direction
- Features.Dungeon.Start uses Features.Quest, so a change to Features.Quest can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Quest.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→18 Features.Dungeon.Start uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Shop.IPaymentService
- Direction
- Features.Dungeon.Start uses Features.Shop, so a change to Features.Shop can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Shop.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→22 Features.Dungeon.Start uses Features.Event✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Event.IEventService
- Direction
- Features.Dungeon.Start uses Features.Event, so a change to Features.Event can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Event.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→23 Features.Dungeon.Start uses Features.Dungeon✕
- Connections
- 6 pairs of types, where a type in Features.Dungeon.Start uses a type in Features.Dungeon.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Features.Dungeon.IDungeonServiceDragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Features.Dungeon.IDungeonStartServiceDragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Features.Dungeon.IOddsInfoServiceDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Dungeon.IDungeonRepositoryDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Dungeon.IDungeonServiceDragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Dungeon.IDungeonStartService
- Direction
- Features.Dungeon.Start uses Features.Dungeon, so a change to Features.Dungeon can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Dungeon.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→25 Features.Dungeon.Start uses Features.Tutorial✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.Dungeon.Start uses Features.Tutorial, so a change to Features.Tutorial can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Tutorial.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→30 Features.Dungeon.Start uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Dungeon.Start uses Features.Shared, so a change to Features.Shared can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Shared.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
33→32 Features.Dungeon.Start uses Features.Fort✕
- Connections
- 1 pair of types, where a type in Features.Dungeon.Start uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Dungeon.Start.DungeonStartService→DragaliaAPI.Features.Fort.IBonusService
- Direction
- Features.Dungeon.Start uses Features.Fort, so a change to Features.Fort can break Features.Dungeon.Start, while a change to Features.Dungeon.Start can't break Features.Fort.
- Position
- Below the diagonal: Features.Dungeon.Start uses a module listed above it, which is the healthy direction.
34→1 Features.Parties uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Parties uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Parties, while a change to Features.Parties can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→2 Features.Parties uses Shared.Definitions.Enums✕
- Connections
- 6 pairs of types, where a type in Features.Parties uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Parties.BonusParams→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Parties.BonusParams→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.Definitions.Enums.WeaponBodies
- Direction
- Features.Parties uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Parties, while a change to Features.Parties can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→3 Features.Parties uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Parties.PartyPowerRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Parties uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Parties, while a change to Features.Parties can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→4 Features.Parties uses Database.Entities✕
- Connections
- 12 pairs of types, where a type in Features.Parties uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Parties.IPartyPowerRepository→DragaliaAPI.Database.Entities.DbPartyPowerDragaliaAPI.Features.Parties.IPartyPowerService→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Features.Parties.IPartyPowerService→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Parties.PartyPowerRepository→DragaliaAPI.Database.Entities.DbPartyPowerDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbPlayerDragonReliabilityDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbTalismanDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Entities.DbWeaponBody
- Direction
- Features.Parties uses Database.Entities, so a change to Database.Entities can break Features.Parties, while a change to Features.Parties can't break Database.Entities.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→6 Features.Parties uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Parties uses Infrastructure, so a change to Infrastructure can break Features.Parties, while a change to Features.Parties can't break Infrastructure.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→7 Features.Parties uses Shared.MasterAsset.Models✕
- Connections
- 5 pairs of types, where a type in Features.Parties uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.MasterAsset.Models.CharaDataDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.MasterAsset.Models.DragonDataDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.MasterAsset.Models.DragonRarityDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.MasterAsset.Models.WeaponBodyDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Shared.MasterAsset.Models.WeaponBodyRarity
- Direction
- Features.Parties uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.Parties, while a change to Features.Parties can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→8 Features.Parties uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Parties uses a type in Database.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Parties.PartyPowerRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Parties uses Database, so a change to Database can break Features.Parties, while a change to Features.Parties can't break Database.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→9 Features.Parties uses Models.Generated✕
- Connections
- 3 pairs of types, where a type in Features.Parties uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Parties.IPartyPowerService→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Parties.Log→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Models.Generated.PartySettingList
- Direction
- Features.Parties uses Models.Generated, so a change to Models.Generated can break Features.Parties, while a change to Features.Parties can't break Models.Generated.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→10 Features.Parties uses Database.Repositories✕
- Connections
- 4 pairs of types, where a type in Features.Parties uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Database.Repositories.IUnitRepositoryDragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Database.Repositories.IUnitRepository
- Direction
- Features.Parties uses Database.Repositories, so a change to Database.Repositories can break Features.Parties, while a change to Features.Parties can't break Database.Repositories.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→30 Features.Parties uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Parties uses Features.Shared, so a change to Features.Shared can break Features.Parties, while a change to Features.Parties can't break Features.Shared.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→32 Features.Parties uses Features.Fort✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Features.Fort.IBonusService
- Direction
- Features.Parties uses Features.Fort, so a change to Features.Fort can break Features.Parties, while a change to Features.Parties can't break Features.Fort.
- Position
- Below the diagonal: Features.Parties uses a module listed above it, which is the healthy direction.
34→36 Features.Parties uses Features.Missions part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Parties.PartyController→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.Parties uses Features.Missions, so a change to Features.Missions can break Features.Parties, while a change to Features.Parties can't break Features.Missions.
- 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.
34→37 Features.Parties uses Features.AbilityCrests part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Parties uses a type in Features.AbilityCrests.
- The types involved
DragaliaAPI.Features.Parties.PartyPowerService→DragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository
- Direction
- Features.Parties uses Features.AbilityCrests, so a change to Features.AbilityCrests can break Features.Parties, while a change to Features.Parties can't break Features.AbilityCrests.
- 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.
35→2 Features.Missions.InitialProgress uses Shared.Definitions.Enums✕
- Connections
- 10 pairs of types, where a type in Features.Missions.InitialProgress uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.PlusCountTypeDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.QuestPlayModeTypesDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.VariationTypesDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Shared.Definitions.Enums.WeaponSeries
- Direction
- Features.Missions.InitialProgress uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→4 Features.Missions.InitialProgress uses Database.Entities✕
- Connections
- 2 pairs of types, where a type in Features.Missions.InitialProgress uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.IMissionInitialProgressionService→DragaliaAPI.Database.Entities.DbPlayerMissionDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Database.Entities.DbPlayerMission
- Direction
- Features.Missions.InitialProgress uses Database.Entities, so a change to Database.Entities can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Database.Entities.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→8 Features.Missions.InitialProgress uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Missions.InitialProgress uses a type in Database.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Missions.InitialProgress.WallCalculator→DragaliaAPI.Database.ApiContext
- Direction
- Features.Missions.InitialProgress uses Database, so a change to Database can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Database.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→10 Features.Missions.InitialProgress uses Database.Repositories✕
- Connections
- 3 pairs of types, where a type in Features.Missions.InitialProgress uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Database.Repositories.IUnitRepositoryDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Database.Repositories.IWeaponRepository
- Direction
- Features.Missions.InitialProgress uses Database.Repositories, so a change to Database.Repositories can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Database.Repositories.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→20 Features.Missions.InitialProgress uses Features.Trade✕
- Connections
- 1 pair of types, where a type in Features.Missions.InitialProgress uses a type in Features.Trade.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Trade.ITradeRepository
- Direction
- Features.Missions.InitialProgress uses Features.Trade, so a change to Features.Trade can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.Trade.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→22 Features.Missions.InitialProgress uses Features.Event✕
- Connections
- 1 pair of types, where a type in Features.Missions.InitialProgress uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Missions.InitialProgress uses Features.Event, so a change to Features.Event can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.Event.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→26 Features.Missions.InitialProgress uses Features.Story✕
- Connections
- 1 pair of types, where a type in Features.Missions.InitialProgress uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Story.IStoryRepository
- Direction
- Features.Missions.InitialProgress uses Features.Story, so a change to Features.Story can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.Story.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→34 Features.Missions.InitialProgress uses Features.Parties✕
- Connections
- 1 pair of types, where a type in Features.Missions.InitialProgress uses a type in Features.Parties.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Parties.IPartyPowerRepository
- Direction
- Features.Missions.InitialProgress uses Features.Parties, so a change to Features.Parties can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.Parties.
- Position
- Below the diagonal: Features.Missions.InitialProgress uses a module listed above it, which is the healthy direction.
35→36 Features.Missions.InitialProgress uses Features.Missions part of a loop✕
- Connections
- 2 pairs of types, where a type in Features.Missions.InitialProgress uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Missions.FortDataServiceDragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.Missions.IMissionRepository
- Direction
- Features.Missions.InitialProgress uses Features.Missions, so a change to Features.Missions can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.Missions.
- 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.
35→37 Features.Missions.InitialProgress uses Features.AbilityCrests part of a loop✕
- Connections
- 1 pair of types, where a type in Features.Missions.InitialProgress uses a type in Features.AbilityCrests.
- The types involved
DragaliaAPI.Features.Missions.InitialProgress.MissionInitialProgressionService→DragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository
- Direction
- Features.Missions.InitialProgress uses Features.AbilityCrests, so a change to Features.AbilityCrests can break Features.Missions.InitialProgress, while a change to Features.Missions.InitialProgress can't break Features.AbilityCrests.
- 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.
36→1 Features.Missions uses Infrastructure.Results✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Missions uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Missions, while a change to Features.Missions can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→2 Features.Missions uses Shared.Definitions.Enums✕
- Connections
- 28 pairs of types, where a type in Features.Missions uses a type in Shared.Definitions.Enums. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DragaliaAPI.Features.Missions.FortDataService→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Missions.FortMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.FortMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Missions.IFortMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.IFortMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.FortPlantsDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.DragonGiftsDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.PlusCountTypeDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.QuestPlayModeTypesDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.UnitElementDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.VariationTypesDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.WeaponBodiesDragaliaAPI.Features.Missions.IMissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.WeaponSeriesDragaliaAPI.Features.Missions.Mission→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.DragonGiftsDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.DragonIdDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.EntityTypesDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.PlusCountTypeDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.QuestPlayModeTypesDragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Shared.Definitions.Enums.UnitElement
- Direction
- Features.Missions uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Missions, while a change to Features.Missions can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→3 Features.Missions uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Missions.MissionRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Missions uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Missions, while a change to Features.Missions can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→4 Features.Missions uses Database.Entities✕
- Connections
- 6 pairs of types, where a type in Features.Missions uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Missions.IMissionRepository→DragaliaAPI.Database.Entities.DbCompletedDailyMissionDragaliaAPI.Features.Missions.IMissionRepository→DragaliaAPI.Database.Entities.DbPlayerMissionDragaliaAPI.Features.Missions.IMissionService→DragaliaAPI.Database.Entities.DbPlayerMissionDragaliaAPI.Features.Missions.MissionRepository→DragaliaAPI.Database.Entities.DbCompletedDailyMissionDragaliaAPI.Features.Missions.MissionRepository→DragaliaAPI.Database.Entities.DbPlayerMissionDragaliaAPI.Features.Missions.MissionService→DragaliaAPI.Database.Entities.DbPlayerMission
- Direction
- Features.Missions uses Database.Entities, so a change to Database.Entities can break Features.Missions, while a change to Features.Missions can't break Database.Entities.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→5 Features.Missions uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Missions.MissionService→DragaliaAPI.Features.Shared.Options.EventOptions
- Direction
- Features.Missions uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Missions, while a change to Features.Missions can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→6 Features.Missions uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Missions uses Infrastructure, so a change to Infrastructure can break Features.Missions, while a change to Features.Missions can't break Infrastructure.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→8 Features.Missions uses Database✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Database.
- The types involved
DragaliaAPI.Features.Missions.MissionRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.Missions uses Database, so a change to Database can break Features.Missions, while a change to Features.Missions can't break Database.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→9 Features.Missions uses Models.Generated✕
- Connections
- 9 pairs of types, where a type in Features.Missions uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionGetMissionListResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveAlbumRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveBeginnerRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveDailyRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveMainStoryRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveMemoryEventRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveNormalRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceivePeriodRewardResponseDragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Models.Generated.MissionReceiveSpecialRewardResponse
- Direction
- Features.Missions uses Models.Generated, so a change to Models.Generated can break Features.Missions, while a change to Features.Missions can't break Models.Generated.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→10 Features.Missions uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Missions.MissionService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Missions uses Database.Repositories, so a change to Database.Repositories can break Features.Missions, while a change to Features.Missions can't break Database.Repositories.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→16 Features.Missions uses Features.Shared.Reward✕
- Connections
- 2 pairs of types, where a type in Features.Missions uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Missions.MissionService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Missions uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Missions, while a change to Features.Missions can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→30 Features.Missions uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Missions.MissionController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Missions uses Features.Shared, so a change to Features.Shared can break Features.Missions, while a change to Features.Missions can't break Features.Shared.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→32 Features.Missions uses Features.Fort✕
- Connections
- 1 pair of types, where a type in Features.Missions uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Missions.FortDataService→DragaliaAPI.Features.Fort.IFortRepository
- Direction
- Features.Missions uses Features.Fort, so a change to Features.Fort can break Features.Missions, while a change to Features.Missions can't break Features.Fort.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
36→35 Features.Missions uses Features.Missions.InitialProgress✕
- Connections
- 2 pairs of types, where a type in Features.Missions uses a type in Features.Missions.InitialProgress.
- The types involved
DragaliaAPI.Features.Missions.MissionProgressionService→DragaliaAPI.Features.Missions.InitialProgress.IMissionInitialProgressionServiceDragaliaAPI.Features.Missions.MissionService→DragaliaAPI.Features.Missions.InitialProgress.IMissionInitialProgressionService
- Direction
- Features.Missions uses Features.Missions.InitialProgress, so a change to Features.Missions.InitialProgress can break Features.Missions, while a change to Features.Missions can't break Features.Missions.InitialProgress.
- Position
- Below the diagonal: Features.Missions uses a module listed above it, which is the healthy direction.
37→1 Features.AbilityCrests uses Infrastructure.Results✕
- Connections
- 3 pairs of types, where a type in Features.AbilityCrests uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Infrastructure.Results.ResultCodeDragaliaAPI.Features.AbilityCrests.IAbilityCrestService→DragaliaAPI.Infrastructure.Results.ResultCode
- Direction
- Features.AbilityCrests uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→2 Features.AbilityCrests uses Shared.Definitions.Enums✕
- Connections
- 9 pairs of types, where a type in Features.AbilityCrests uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestRepository→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Shared.Definitions.Enums.MaterialsDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Shared.Definitions.Enums.PlusCountTypeDragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.AbilityCrests.IAbilityCrestService→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.AbilityCrests.IAbilityCrestService→DragaliaAPI.Shared.Definitions.Enums.PlusCountTypeDragaliaAPI.Features.AbilityCrests.Log→DragaliaAPI.Shared.Definitions.Enums.AbilityCrestIdDragaliaAPI.Features.AbilityCrests.Log→DragaliaAPI.Shared.Definitions.Enums.PlusCountType
- Direction
- Features.AbilityCrests uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→3 Features.AbilityCrests uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestRepository→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.AbilityCrests uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→4 Features.AbilityCrests uses Database.Entities✕
- Connections
- 5 pairs of types, where a type in Features.AbilityCrests uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestRepository→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.AbilityCrests.AbilityCrestRepository→DragaliaAPI.Database.Entities.DbAbilityCrestSetDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.AbilityCrests.IAbilityCrestRepository→DragaliaAPI.Database.Entities.DbAbilityCrestSet
- Direction
- Features.AbilityCrests uses Database.Entities, so a change to Database.Entities can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Database.Entities.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→6 Features.AbilityCrests uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.AbilityCrests uses Infrastructure, so a change to Infrastructure can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Infrastructure.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→7 Features.AbilityCrests uses Shared.MasterAsset.Models✕
- Connections
- 3 pairs of types, where a type in Features.AbilityCrests uses a type in Shared.MasterAsset.Models.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Shared.MasterAsset.Models.AbilityCrestDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Shared.MasterAsset.Models.AbilityCrestRarityDragaliaAPI.Features.AbilityCrests.IAbilityCrestService→DragaliaAPI.Shared.MasterAsset.Models.AbilityCrest
- Direction
- Features.AbilityCrests uses Shared.MasterAsset.Models, so a change to Shared.MasterAsset.Models can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Shared.MasterAsset.Models.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→8 Features.AbilityCrests uses Database✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Database.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestRepository→DragaliaAPI.Database.ApiContext
- Direction
- Features.AbilityCrests uses Database, so a change to Database can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Database.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→10 Features.AbilityCrests uses Database.Repositories✕
- Connections
- 2 pairs of types, where a type in Features.AbilityCrests uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Database.Repositories.IInventoryRepositoryDragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.AbilityCrests uses Database.Repositories, so a change to Database.Repositories can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Database.Repositories.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→25 Features.AbilityCrests uses Features.Tutorial✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.AbilityCrests uses Features.Tutorial, so a change to Features.Tutorial can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Features.Tutorial.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→30 Features.AbilityCrests uses Features.Shared✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.AbilityCrests uses Features.Shared, so a change to Features.Shared can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Features.Shared.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
37→36 Features.AbilityCrests uses Features.Missions✕
- Connections
- 1 pair of types, where a type in Features.AbilityCrests uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.AbilityCrests.AbilityCrestService→DragaliaAPI.Features.Missions.IMissionProgressionService
- Direction
- Features.AbilityCrests uses Features.Missions, so a change to Features.Missions can break Features.AbilityCrests, while a change to Features.AbilityCrests can't break Features.Missions.
- Position
- Below the diagonal: Features.AbilityCrests uses a module listed above it, which is the healthy direction.
38→1 Features.Login uses Infrastructure.Results✕
- Connections
- 3 pairs of types, where a type in Features.Login uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Login.MypageController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Login.UserController→DragaliaAPI.Infrastructure.Results.DragaliaResult
- Direction
- Features.Login uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Login, while a change to Features.Login can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→3 Features.Login uses Shared.PlayerDetails✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Login.LoginService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Login uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Login, while a change to Features.Login can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→6 Features.Login uses Infrastructure✕
- Connections
- 3 pairs of types, where a type in Features.Login uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Login.MypageController→DragaliaAPI.Infrastructure.DragaliaControllerBaseDragaliaAPI.Features.Login.UserController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Login uses Infrastructure, so a change to Infrastructure can break Features.Login, while a change to Features.Login can't break Infrastructure.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→8 Features.Login uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Login uses a type in Database.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.LoginService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Login uses Database, so a change to Database can break Features.Login, while a change to Features.Login can't break Database.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→10 Features.Login uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Login.UserController→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Login uses Database.Repositories, so a change to Database.Repositories can break Features.Login, while a change to Features.Login can't break Database.Repositories.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→11 Features.Login uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Login.LoginService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Login uses Features.Present, so a change to Features.Present can break Features.Login, while a change to Features.Login can't break Features.Present.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→16 Features.Login uses Features.Shared.Reward✕
- Connections
- 2 pairs of types, where a type in Features.Login uses a type in Features.Shared.Reward.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Features.Shared.Reward.IRewardServiceDragaliaAPI.Features.Login.LoginService→DragaliaAPI.Features.Shared.Reward.IRewardService
- Direction
- Features.Login uses Features.Shared.Reward, so a change to Features.Shared.Reward can break Features.Login, while a change to Features.Login can't break Features.Shared.Reward.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→18 Features.Login uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Login.MypageController→DragaliaAPI.Features.Shop.IShopRepository
- Direction
- Features.Login uses Features.Shop, so a change to Features.Shop can break Features.Login, while a change to Features.Login can't break Features.Shop.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→24 Features.Login uses Features.Wall✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Features.Wall.
- The types involved
DragaliaAPI.Features.Login.LoginService→DragaliaAPI.Features.Wall.IWallService
- Direction
- Features.Login uses Features.Wall, so a change to Features.Wall can break Features.Login, while a change to Features.Login can't break Features.Wall.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→28 Features.Login uses Features.Login.Actions✕
- Connections
- 2 pairs of types, where a type in Features.Login uses a type in Features.Login.Actions.
- The types involved
DragaliaAPI.Features.Login.Log→DragaliaAPI.Features.Login.Actions.IDailyResetActionDragaliaAPI.Features.Login.LoginController→DragaliaAPI.Features.Login.Actions.IDailyResetAction
- Direction
- Features.Login uses Features.Login.Actions, so a change to Features.Login.Actions can break Features.Login, while a change to Features.Login can't break Features.Login.Actions.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→30 Features.Login uses Features.Shared✕
- Connections
- 4 pairs of types, where a type in Features.Login uses a type in Features.Shared.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Login.MypageController→DragaliaAPI.Features.Shared.IUpdateDataServiceDragaliaAPI.Features.Login.UserController→DragaliaAPI.Features.Shared.IBaasApiDragaliaAPI.Features.Login.UserController→DragaliaAPI.Features.Shared.IUpdateDataService
- Direction
- Features.Login uses Features.Shared, so a change to Features.Shared can break Features.Login, while a change to Features.Login can't break Features.Shared.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→31 Features.Login uses Features.Dragons✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Features.Dragons.
- The types involved
DragaliaAPI.Features.Login.LoginController→DragaliaAPI.Features.Dragons.IDragonService
- Direction
- Features.Login uses Features.Dragons, so a change to Features.Dragons can break Features.Login, while a change to Features.Login can't break Features.Dragons.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
38→36 Features.Login uses Features.Missions✕
- Connections
- 1 pair of types, where a type in Features.Login uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Login.MypageController→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Login uses Features.Missions, so a change to Features.Missions can break Features.Login, while a change to Features.Login can't break Features.Missions.
- Position
- Below the diagonal: Features.Login uses a module listed above it, which is the healthy direction.
39→2 Features.Login.SavefileUpdate uses Shared.Definitions.Enums✕
- Connections
- 2 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V18Update→DragaliaAPI.Shared.Definitions.Enums.QuestWallTypesDragaliaAPI.Features.Login.SavefileUpdate.V1Update→DragaliaAPI.Shared.Definitions.Enums.FortPlants
- Direction
- Features.Login.SavefileUpdate uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→3 Features.Login.SavefileUpdate uses Shared.PlayerDetails✕
- Connections
- 10 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.SavefileUpdateService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V17Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V19Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V21Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V23Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V24Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V25Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V28Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V2Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.SavefileUpdate.V9Update→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Login.SavefileUpdate uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→8 Features.Login.SavefileUpdate uses Database✕
- Connections
- 14 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Database.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.SavefileUpdateService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V14Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V17Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V19Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V20Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V21Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V22Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V23Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V24Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V25Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V26Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V27Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V28Update→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.SavefileUpdate.V9Update→DragaliaAPI.Database.ApiContext
- Direction
- Features.Login.SavefileUpdate uses Database, so a change to Database can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Database.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→10 Features.Login.SavefileUpdate uses Database.Repositories✕
- Connections
- 6 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V10Update→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V11Update→DragaliaAPI.Database.Repositories.IPartyRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V1Update→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V4Update→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V5Update→DragaliaAPI.Database.Repositories.IUserDataRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V8Update→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Login.SavefileUpdate uses Database.Repositories, so a change to Database.Repositories can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Database.Repositories.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→11 Features.Login.SavefileUpdate uses Features.Present✕
- Connections
- 3 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V20Update→DragaliaAPI.Features.Present.IPresentServiceDragaliaAPI.Features.Login.SavefileUpdate.V22Update→DragaliaAPI.Features.Present.IPresentServiceDragaliaAPI.Features.Login.SavefileUpdate.V26Update→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Login.SavefileUpdate uses Features.Present, so a change to Features.Present can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Present.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→14 Features.Login.SavefileUpdate uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V22Update→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Login.SavefileUpdate uses Features.Player, so a change to Features.Player can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Player.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→18 Features.Login.SavefileUpdate uses Features.Shop✕
- Connections
- 1 pair of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Shop.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V3Update→DragaliaAPI.Features.Shop.IShopRepository
- Direction
- Features.Login.SavefileUpdate uses Features.Shop, so a change to Features.Shop can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Shop.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→22 Features.Login.SavefileUpdate uses Features.Event✕
- Connections
- 2 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Event.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V13Update→DragaliaAPI.Features.Event.IEventRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V16Update→DragaliaAPI.Features.Event.IEventRepository
- Direction
- Features.Login.SavefileUpdate uses Features.Event, so a change to Features.Event can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Event.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→24 Features.Login.SavefileUpdate uses Features.Wall✕
- Connections
- 3 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Wall.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V15Update→DragaliaAPI.Features.Wall.IWallServiceDragaliaAPI.Features.Login.SavefileUpdate.V18Update→DragaliaAPI.Features.Wall.IWallServiceDragaliaAPI.Features.Login.SavefileUpdate.V21Update→DragaliaAPI.Features.Wall.IWallService
- Direction
- Features.Login.SavefileUpdate uses Features.Wall, so a change to Features.Wall can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Wall.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→25 Features.Login.SavefileUpdate uses Features.Tutorial✕
- Connections
- 2 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Tutorial.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V4Update→DragaliaAPI.Features.Tutorial.ITutorialServiceDragaliaAPI.Features.Login.SavefileUpdate.V7Update→DragaliaAPI.Features.Tutorial.ITutorialService
- Direction
- Features.Login.SavefileUpdate uses Features.Tutorial, so a change to Features.Tutorial can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Tutorial.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→26 Features.Login.SavefileUpdate uses Features.Story✕
- Connections
- 7 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Story.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V14Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V15Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V18Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V1Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V4Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V7Update→DragaliaAPI.Features.Story.IStoryRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V9Update→DragaliaAPI.Features.Story.IStoryRepository
- Direction
- Features.Login.SavefileUpdate uses Features.Story, so a change to Features.Story can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Story.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→32 Features.Login.SavefileUpdate uses Features.Fort✕
- Connections
- 5 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V11Update→DragaliaAPI.Features.Fort.IBonusServiceDragaliaAPI.Features.Login.SavefileUpdate.V1Update→DragaliaAPI.Features.Fort.IFortRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V4Update→DragaliaAPI.Features.Fort.IFortRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V5Update→DragaliaAPI.Features.Fort.IFortRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V6Update→DragaliaAPI.Features.Fort.IFortRepository
- Direction
- Features.Login.SavefileUpdate uses Features.Fort, so a change to Features.Fort can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Fort.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→34 Features.Login.SavefileUpdate uses Features.Parties✕
- Connections
- 2 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Parties.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V11Update→DragaliaAPI.Features.Parties.IPartyPowerRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V11Update→DragaliaAPI.Features.Parties.IPartyPowerService
- Direction
- Features.Login.SavefileUpdate uses Features.Parties, so a change to Features.Parties can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Parties.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→35 Features.Login.SavefileUpdate uses Features.Missions.InitialProgress✕
- Connections
- 1 pair of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Missions.InitialProgress.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V12Update→DragaliaAPI.Features.Missions.InitialProgress.IMissionInitialProgressionService
- Direction
- Features.Login.SavefileUpdate uses Features.Missions.InitialProgress, so a change to Features.Missions.InitialProgress can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Missions.InitialProgress.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
39→36 Features.Login.SavefileUpdate uses Features.Missions✕
- Connections
- 4 pairs of types, where a type in Features.Login.SavefileUpdate uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Login.SavefileUpdate.V12Update→DragaliaAPI.Features.Missions.IMissionRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V13Update→DragaliaAPI.Features.Missions.IMissionServiceDragaliaAPI.Features.Login.SavefileUpdate.V18Update→DragaliaAPI.Features.Missions.IMissionRepositoryDragaliaAPI.Features.Login.SavefileUpdate.V18Update→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Login.SavefileUpdate uses Features.Missions, so a change to Features.Missions can break Features.Login.SavefileUpdate, while a change to Features.Login.SavefileUpdate can't break Features.Missions.
- Position
- Below the diagonal: Features.Login.SavefileUpdate uses a module listed above it, which is the healthy direction.
40→1 Features.Login.Savefile uses Infrastructure.Results✕
- Connections
- 2 pairs of types, where a type in Features.Login.Savefile uses a type in Infrastructure.Results.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadController→DragaliaAPI.Infrastructure.Results.DragaliaResultDragaliaAPI.Features.Login.Savefile.SavefileController→DragaliaAPI.Infrastructure.Results.DragaliaResponse
- Direction
- Features.Login.Savefile uses Infrastructure.Results, so a change to Infrastructure.Results can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Infrastructure.Results.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→2 Features.Login.Savefile uses Shared.Definitions.Enums✕
- Connections
- 5 pairs of types, where a type in Features.Login.Savefile uses a type in Shared.Definitions.Enums.
- The types involved
DragaliaAPI.Features.Login.Savefile.DefaultSavefileData→DragaliaAPI.Shared.Definitions.Enums.CharasDragaliaAPI.Features.Login.Savefile.DefaultSavefileData→DragaliaAPI.Shared.Definitions.Enums.EmblemsDragaliaAPI.Features.Login.Savefile.GenericStory→DragaliaAPI.Shared.Definitions.Enums.StoryStateDragaliaAPI.Features.Login.Savefile.GenericStory→DragaliaAPI.Shared.Definitions.Enums.StoryTypesDragaliaAPI.Features.Login.Savefile.GenericTrade→DragaliaAPI.Shared.Definitions.Enums.TradeType
- Direction
- Features.Login.Savefile uses Shared.Definitions.Enums, so a change to Shared.Definitions.Enums can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Shared.Definitions.Enums.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→3 Features.Login.Savefile uses Shared.PlayerDetails✕
- Connections
- 3 pairs of types, where a type in Features.Login.Savefile uses a type in Shared.PlayerDetails.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.Savefile.SavefileController→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityServiceDragaliaAPI.Features.Login.Savefile.SavefileService→DragaliaAPI.Shared.PlayerDetails.IPlayerIdentityService
- Direction
- Features.Login.Savefile uses Shared.PlayerDetails, so a change to Shared.PlayerDetails can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Shared.PlayerDetails.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→4 Features.Login.Savefile uses Database.Entities✕
- Connections
- 12 pairs of types, where a type in Features.Login.Savefile uses a type in Database.Entities.
- The types involved
DragaliaAPI.Features.Login.Savefile.ISavefileService→DragaliaAPI.Database.Entities.DbPlayerDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbAbilityCrestDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPartyDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPartyUnitDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPlayerDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPlayerCharaDataDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPlayerDragonDataDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPlayerDragonReliabilityDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbPlayerUserDataDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Database.Entities.DbWeaponBodyDragaliaAPI.Features.Login.Savefile.Savefile→DragaliaAPI.Database.Entities.DbPlayerShopInfoDragaliaAPI.Features.Login.Savefile.SavefileService→DragaliaAPI.Database.Entities.DbPlayer
- Direction
- Features.Login.Savefile uses Database.Entities, so a change to Database.Entities can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Database.Entities.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→5 Features.Login.Savefile uses Features.Shared.Options✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Shared.Options.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Shared.Options.PhotonOptions
- Direction
- Features.Login.Savefile uses Features.Shared.Options, so a change to Features.Shared.Options can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Shared.Options.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→6 Features.Login.Savefile uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Infrastructure.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadController→DragaliaAPI.Infrastructure.DragaliaControllerBase
- Direction
- Features.Login.Savefile uses Infrastructure, so a change to Infrastructure can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Infrastructure.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→8 Features.Login.Savefile uses Database✕
- Connections
- 2 pairs of types, where a type in Features.Login.Savefile uses a type in Database.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Database.ApiContextDragaliaAPI.Features.Login.Savefile.SavefileService→DragaliaAPI.Database.ApiContext
- Direction
- Features.Login.Savefile uses Database, so a change to Database can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Database.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→9 Features.Login.Savefile uses Models.Generated✕
- Connections
- 12 pairs of types, where a type in Features.Login.Savefile uses a type in Models.Generated.
- The types involved
DragaliaAPI.Features.Login.Savefile.ILoadService→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Login.Savefile.ISavefileService→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Models.Generated.DragonListDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Models.Generated.PartySettingListDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Models.Generated.UserDataDragaliaAPI.Features.Login.Savefile.LoadMapper→DragaliaAPI.Models.Generated.WeaponBodyListDragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Login.Savefile.Savefile→DragaliaAPI.Models.Generated.DragonListDragaliaAPI.Features.Login.Savefile.Savefile→DragaliaAPI.Models.Generated.UserDataDragaliaAPI.Features.Login.Savefile.Savefile→DragaliaAPI.Models.Generated.WeaponBodyListDragaliaAPI.Features.Login.Savefile.SavefileController→DragaliaAPI.Models.Generated.LoadIndexResponseDragaliaAPI.Features.Login.Savefile.SavefileService→DragaliaAPI.Models.Generated.LoadIndexResponse
- Direction
- Features.Login.Savefile uses Models.Generated, so a change to Models.Generated can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Models.Generated.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→10 Features.Login.Savefile uses Database.Repositories✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Database.Repositories.
- The types involved
DragaliaAPI.Features.Login.Savefile.SavefileController→DragaliaAPI.Database.Repositories.IUserDataRepository
- Direction
- Features.Login.Savefile uses Database.Repositories, so a change to Database.Repositories can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Database.Repositories.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→11 Features.Login.Savefile uses Features.Present✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Present.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Present.IPresentService
- Direction
- Features.Login.Savefile uses Features.Present, so a change to Features.Present can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Present.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→14 Features.Login.Savefile uses Features.Player✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Player.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Player.IUserService
- Direction
- Features.Login.Savefile uses Features.Player, so a change to Features.Player can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Player.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→20 Features.Login.Savefile uses Features.Trade✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Trade.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Trade.ITradeService
- Direction
- Features.Login.Savefile uses Features.Trade, so a change to Features.Trade can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Trade.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→27 Features.Login.Savefile uses Features.Summoning✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Summoning.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Summoning.SummonService
- Direction
- Features.Login.Savefile uses Features.Summoning, so a change to Features.Summoning can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Summoning.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→32 Features.Login.Savefile uses Features.Fort✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Fort.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Fort.IBonusService
- Direction
- Features.Login.Savefile uses Features.Fort, so a change to Features.Fort can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Fort.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→36 Features.Login.Savefile uses Features.Missions✕
- Connections
- 1 pair of types, where a type in Features.Login.Savefile uses a type in Features.Missions.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadService→DragaliaAPI.Features.Missions.IMissionService
- Direction
- Features.Login.Savefile uses Features.Missions, so a change to Features.Missions can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Missions.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
40→39 Features.Login.Savefile uses Features.Login.SavefileUpdate✕
- Connections
- 2 pairs of types, where a type in Features.Login.Savefile uses a type in Features.Login.SavefileUpdate.
- The types involved
DragaliaAPI.Features.Login.Savefile.LoadController→DragaliaAPI.Features.Login.SavefileUpdate.ISavefileUpdateServiceDragaliaAPI.Features.Login.Savefile.SavefileService→DragaliaAPI.Features.Login.SavefileUpdate.ISavefileUpdate
- Direction
- Features.Login.Savefile uses Features.Login.SavefileUpdate, so a change to Features.Login.SavefileUpdate can break Features.Login.Savefile, while a change to Features.Login.Savefile can't break Features.Login.SavefileUpdate.
- Position
- Below the diagonal: Features.Login.Savefile uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 73 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 38 | High / Critical |
| A02:2025 — Security Misconfiguration | 9 | Medium |
| A07:2025 — Authentication Failures | 8 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene; Resolve the 1 finding(s) in DR & Backup.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. | +5.2 pts | Low | Dependency Hygiene |
| Resolve the 7 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +3.9 pts | Low | Secrets (history) |
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +7.4 pts | Medium | Data Protection |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, REDACTED. | +3.4 pts | Low | Dependency Hygiene |
| Resolve the 1 finding(s) in DR & Backup. | +4.1 pts | Medium | DR & Backup |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them. | +3.6 pts | Medium | Web-Security Posture |
| Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED, REDACTED. | +3.3 pts | Medium | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| DragaliaAPI/DragaliaAPI/Features/Login/Auth/SessionService.cs | 4.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 78 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 78 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 585 of 657 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 927 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 11 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifests: REDACTED, Website/package.json — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read them, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (14 contributor(s) across 1422 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 13 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (87,274 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/EventIdAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/MissionTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/WallTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Program.cs`, `DragaliaAPI/DragaliaAPI.Shared.SourceGenerator/EquatableReadOnlyList.cs`, … (+184 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX7 Slice cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 278 further occurrence(s) are not listed individually; the score already reflects all 318.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 513 further occurrence(s) are not listed individually; the score already reflects all 553.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UpdateDataService.MapUpdateDataList at 52. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being QuestCompletionService.IsQuestMissionCompleted at 37 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: DragaliaAPI/DragaliaAPI/Features/Dungeon/QuestCompletionService.cs (QuestCompletionService.IsQuestMissionCompleted at 37), DragaliaAPI/DragaliaAPI/Features/Shared/Reward/Handlers/GenericRewardHandler.cs (GenericRewardHandler.Grant at 22), DragaliaAPI/DragaliaAPI/Features/Web/Savefile/SavefileEditService.cs (SavefileEditService.ValidatePresents at 22), DragaliaAPI/DragaliaAPI/Features/Summoning/SummonService.cs (SummonService.ProcessSummonPayment at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UpdateDataService.MapUpdateDataList (cyclomatic 52), MissionInitialProgressionService.GetInitialMissionProgress (cyclomatic 49), CharaController.CharaManaNodeUnlock (cyclomatic 42). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
26 method(s) exceeded the cognitive complexity threshold of 15; the worst was CharaController.CharaManaNodeUnlock at 71.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with CharaController.CharaManaNodeUnlock (cognitive 71), ClearPartyService.ProcessLostUnitList (cognitive 37), MissionProgressionService.ProcessMissionEvents (cognitive 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.4 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
25 god class(es) detected.
What to do
- Resolve the 11 MethodTooLong finding(s) in God Classes — start with DungeonRepository.cs (2), QuestHelper.Data.cs, UpdateDataService.cs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 8 ClassTooLong finding(s) in God Classes — start with StaticHelperDataService.cs, V1Missions.cs, DmodeDungeonService.cs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 FileTooLong finding(s) in God Classes — start with StaticHelperDataService.cs, V1Missions.cs, DragonService.cs. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
21 duplicated block group(s) detected. 2.7 % of the production lines (2,356 of 87,274) are in a reported copy. A further 44 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 6 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with EventService.cs, MissionInitialProgressionService.cs, SummonOddsLogic.cs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with DmodeController.cs, RedisGame.cs, DiscordPlugin.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CharaController.cs, MissionInitialProgressionService.cs, StoryService.cs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
19 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 155 classes have LCOM4 above 3.
D10 · Test Quality
3 skipped (3 with a documented reason), 0 zero-assertion, 6 mock references across 927 tests. Measured on the C# suite only — at least 11 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 3 measured tier(s). integration: measured (0 flaky); other: measured (0 flaky); JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in MaintenanceWorker/ (4 tests)): measured (0 flaky).
D12 · Dependency Hygiene
42 outdated, 2 vulnerable, 1 deprecated, 4 prerelease packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
What to do
- Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 248 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 76 direct `PackageReference`(s), and 174 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest and REDACTED, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs (3 of 3 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with EventDropService.cs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
107 deducted debt markers + 43 dead symbols across 87274 LoC in the .NET projects (0.4/KLoC) → score 9.2.
What to do
- Resolve the 7 WriteOnlyPrivateField finding(s) in Explicit Debt — start with SessionService.cs (2), InputOutputFormatters.cs (2), MaintenanceTest.cs. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 75 TodoComment finding(s) in Explicit Debt — start with DragonService.cs (5), EventDropService.cs (4), PartyController.cs (4). — One of this dimension's main actionable groups (75 warning-level).
- Resolve the 43 Dead code finding(s) in Explicit Debt — start with ModuleInitializer.cs (4), DbPlayerBannerDataFactory.cs, IQuestRepository.cs. — One of this dimension's main actionable groups (43 warning-level).
D18 · Solution Shape
19 projects, 1133 source files, 124054 hand-written lines of code (87274 production / 36780 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 95813 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 29 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 8 document(s) read across 14 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 23 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `AttackBaseOnHPUpRate` spells `HP` where 22 names in the project spell… finding(s) in Naming Consistency — start with AbilityTypes.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 483 judged comments only repeat the code they sit on (0.2 %). 633 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with TreasureTradeResetTest.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 19 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with DragaliaAPI.csproj, DragaliaAPI.Shared.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Split DragaliaAPI.Shared finding(s) in Project Cohesion — start with DragaliaAPI.Shared.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
100 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
D28 · Secrets (history)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 7 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
73 finding(s): 0 critical, 62 high, 11 medium, 0 low. 34 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 204 file(s) — `DragaliaAPI/DragaliaAPI.Integration.Test/Features/AbilityCrests/AbilityCrestTest.cs` (line 263, line 285), `DragaliaAPI/DragaliaAPI.Integration.Test/Features/Dungeon/AutoRepeatTest.cs` (line 402), `DragaliaAPI/DragaliaAPI.Integration.Test/Features/Dungeon/DungeonRecordTest.cs` (line 675, line 677, line 679, …), `DragaliaAPI/DragaliaAPI.Integration.Test/Features/Missions/MissionTest.cs` (lines 713–721, line 725), `DragaliaAPI/DragaliaAPI.Integration.Test/Features/Present/PresentTest.cs` (line 583, line 666), … (+199 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 181 of those file(s) — `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/EventIdAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/MissionTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/WallTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.Shared.SourceGenerator/EquatableReadOnlyList.cs`, `DragaliaAPI/DragaliaAPI.Shared/Features/StorySkip/StorySkipRewards.cs`, … (+176 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 11 of those file(s) — `DragaliaAPI/DragaliaAPI.Integration.Test/Features/Missions/MissionTest.cs`, `DragaliaAPI/DragaliaAPI.Shared.SourceGenerator/MasterAssetGenerator.cs`, `DragaliaAPI/DragaliaAPI.Test/Features/Summon/SummonOddsLogicTest.cs`, `DragaliaAPI/DragaliaAPI/Extensions/NumberExtensions.cs`, `DragaliaAPI/DragaliaAPI/Features/Event/EventService.cs`, … (+6 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- No action in Static Analysis (SAST) — all 34 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (34 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
21 finding(s): 1 critical, 11 high, 7 medium, 2 low.
What to do
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED, REDACTED. — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 0 high, 6 medium, 3 low.
What to do
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
D34 · Knowledge Freshness
19 of 227 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is DragaliaAPI/DragaliaAPI/Features/Parties/PartyPowerService.cs. Counted over 227 of the 906 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with PartyPowerService.cs, Materials.cs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 17 Orphaned file finding(s) in Knowledge Freshness — start with CharaHonorHelper.cs, UserService.cs, ShopService.cs. — One of this dimension's main actionable groups (17 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: SessionService.cs↔SessionAuthenticationHandler.cs 60%; SessionService.cs↔Program.cs 54%; DragaliaControllerBase.cs↔Program.cs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with SessionService.cs (2), DragaliaControllerBase.cs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — Website/src/routes/(main)/admin/impersonation/+page.svelte:72
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — Website/src/routes/(main)/header.svelte:61
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — MaintenanceWorker/src/web/page.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <loader2icon> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — Website/src/lib/shadcn/components/ui/sonner/sonner.svelte:20
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `Banner` is not registered, but `SystemBanners` creates it and keeps it in the static `RerollBanner`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (summonType, TradeDictionary, pickupCharaData, pickupDragonData; e.g. `summonType` at line 146). — DragaliaAPI/DragaliaAPI/Features/Summoning/SummonBannerOptions.cs:53
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
- The namespaces DragaliaAPI.Database.Entities ↔ DragaliaAPI.Database.Entities.Abstract depend on each other. The lightest dependency in the cycle is DragaliaAPI.Database.Entities.Abstract → DragaliaAPI.Database.Entities (DragaliaAPI.Database.Entities.Abstract.DbPlayerData → DragaliaAPI.Database.Entities.DbPlayer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — DragaliaAPI/DragaliaAPI.Database/Entities/Abstract/DbPlayerData.cs:5
- The namespaces DragaliaAPI.Features.AbilityCrests ↔ DragaliaAPI.Features.Chara ↔ DragaliaAPI.Features.ClearParty ↔ DragaliaAPI.Features.CoOp ↔ DragaliaAPI.Features.Dmode ↔ DragaliaAPI.Features.DmodeDungeon ↔ DragaliaAPI.Features.Dragons ↔ DragaliaAPI.Features.Dungeon ↔ DragaliaAPI.Features.Dungeon.AutoRepeat ↔ DragaliaAPI.Features.Dungeon.Record ↔ DragaliaAPI.Features.Emblem ↔ DragaliaAPI.Features.Event ↔ DragaliaAPI.Features.Fort ↔ DragaliaAPI.Features.Friends ↔ DragaliaAPI.Features.Item ↔ DragaliaAPI.Features.Login.Actions ↔ DragaliaAPI.Features.Missions ↔ DragaliaAPI.Features.Missions.InitialProgress ↔ DragaliaAPI.Features.Parties ↔ DragaliaAPI.Features.Player ↔ DragaliaAPI.Features.Present ↔ DragaliaAPI.Features.Quest ↔ DragaliaAPI.Features.Shared ↔ DragaliaAPI.Features.Shared.Reward ↔ DragaliaAPI.Features.Shared.Reward.Handlers ↔ DragaliaAPI.Features.Shop ↔ DragaliaAPI.Features.Story ↔ DragaliaAPI.Features.Summoning ↔ DragaliaAPI.Features.TimeAttack ↔ DragaliaAPI.Features.Trade ↔ DragaliaAPI.Features.Tutorial ↔ DragaliaAPI.Features.Wall ↔ DragaliaAPI.Infrastructure.Metrics ↔ DragaliaAPI.Models.Generated depend on each other. The lightest dependency in the cycle is DragaliaAPI.Features.AbilityCrests → DragaliaAPI.Features.Missions (DragaliaAPI.Features.AbilityCrests.AbilityCrestService → DragaliaAPI.Features.Missions.IMissionProgressionService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:4
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
- `IUnitRepository` declares 17 members: `Dragons`, `DragonReliabilities`, `WeaponBodies`, `AbilityCrests`, `Talismans`, `RemoveDragons`, `GetCharaSetData`, `AddCharaSetData`, `GetCharaSets`, `GetCharaSets`, `FindCharaAsync`, `FindDragonAsync`, `FindDragonReliabilityAsync`, `FindTalismanAsync`, `FindWeaponBodyAsync`, `AddTalisman`, `RemoveTalisman`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 17 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI.Database/Repositories/IUnitRepository.cs:6
- `IShop` declares 37 members: `Id`, `Limit`, `PaymentType`, `NeedCost`, `DestinationEntityType1`, `DestinationEntityId1`, `DestinationEntityQuantity1`, `DestinationLimitBreakCount1`, `DestinationEntityType2`, `DestinationEntityId2`, `DestinationEntityQuantity2`, `DestinationLimitBreakCount2`, `DestinationEntityType3`, `DestinationEntityId3`, `DestinationEntityQuantity3`, `DestinationLimitBreakCount3`, `DestinationEntityType4`, `DestinationEntityId4`, `DestinationEntityQuantity4`, `DestinationLimitBreakCount4`, `DestinationEntityType5`, `DestinationEntityId5`, `DestinationEntityQuantity5`, `DestinationLimitBreakCount5`, `DestinationEntityType6`, `DestinationEntityId6`, `DestinationEntityQuantity6`, `DestinationLimitBreakCount6`, `DestinationEntityType7`, `DestinationEntityId7`, `DestinationEntityQuantity7`, `DestinationLimitBreakCount7`, `DestinationEntityType8`, `DestinationEntityId8`, `DestinationEntityQuantity8`, `DestinationLimitBreakCount8`, `DestinationEntities`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/Shop/IShop.cs:5
- `IEventRepository` declares 21 members: `EventData`, `Rewards`, `Items`, `Passives`, `GetEventDataAsync`, `GetEventRewardsAsync`, `GetEventRewardIdsAsync`, `GetEventItemAsync`, `GetEventItemAsync`, `GetEventItemsAsync`, `GetEventItemQuantityAsync`, `GetEventPassivesAsync`, `GetEventPassiveAsync`, `CreateEventData`, `CreateEventReward`, `CreateEventItems`, `CreateEventPassives`, `AddItemQuantityAsync`, `RemoveItemQuantityAsync`, `AddEventPassiveProgressAsync`, `HasEventDataAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI/Features/Event/IEventRepository.cs:5
- `IEventService` declares 17 members: `GetCustomEventFlag`, `GetEventRewardList`, `GetEventPassiveList`, `ReceiveEventRewards`, `ReceiveEventLocationReward`, `CreateEventData`, `GetEventCharaFriendshipList`, `GetBuildEventUserData`, `GetRaidEventUserData`, `GetClb01EventUserData`, `GetCollectEventUserData`, `GetCombatEventUserData`, `GetEarnEventUserData`, `GetExHunterEventUserData`, `GetExRushEventUserData`, `GetMazeEventUserData`, `GetSimpleEventUserData`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI/Features/Event/IEventService.cs:5
- `IFortService` declares 19 members: `GetBuildList`, `AddCarpenter`, `GetFortDetail`, `CollectIncome`, `BuildAtOnce`, `LevelupAtOnce`, `CancelBuild`, `CancelLevelup`, `EndBuild`, `EndLevelup`, `BuildStart`, `LevelupStart`, `Move`, `ClearPlantNewStatuses`, `ClearPlantNewStatuses`, `GetRupieProduction`, `GetDragonfruitProduction`, `GetStaminaProduction`, `GetCoreLevels`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI/Features/Fort/IFortService.cs:7
- `IMissionProgressionService` declares 29 members: `OnQuestCleared`, `OnEventGroupCleared`, `OnQuestStoryCleared`, `OnWeaponEarned`, `OnWeaponRefined`, `OnAbilityCrestBuildupPlusCount`, `OnAbilityCrestTotalPlusCountUp`, `OnAbilityCrestLevelUp`, `OnCharacterBuildupPlusCount`, `OnCharacterLevelUp`, `OnCharacterManaNodeUnlock`, `OnDragonLevelUp`, `OnDragonGiftSent`, `OnDragonBondLevelUp`, `OnItemSummon`, `OnPartyOptimized`, `OnAbilityCrestTradeViewed`, `OnGuildCheckInRewardClaimed`, `OnPartyPowerReached`, `OnTreasureTrade`, `OnEventParticipation`, `OnEventRegularBattleCleared`, `OnEventQuestClearedWithCrest`, `OnEventPointCollected`, `OnEventChallengeBattleCleared`, `OnEventTrialCleared`, `OnEventRaidCleared`, `EnqueueEvent`, `ProcessMissionEvents`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DragaliaAPI/DragaliaAPI/Features/Missions/IMissionProgressionService.cs:6
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion
- `AbilityCrestService` (slice 'AbilityCrests') depends on `IMissionProgressionService` from slice 'Missions'. — DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:20
- `AbilityCrestService` (slice 'AbilityCrests') depends on `ITutorialService` from slice 'Tutorial'. — DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:21
- `AbilityCrestService` (slice 'AbilityCrests') depends on `TutorialService.TutorialStatusIds` from slice 'Tutorial'. — DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:68
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IAlbumService` from slice 'Album'. — DragaliaAPI/DragaliaAPI/Features/Album/FeatureExtensions.cs:10
- `FeatureExtensions` (slice 'AbilityCrests') depends on `AlbumService` from slice 'Album'. — DragaliaAPI/DragaliaAPI/Features/Album/FeatureExtensions.cs:10
- `CharaController` (slice 'Chara') depends on `IStoryRepository` from slice 'Story'. — DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:28
- `CharaController` (slice 'Chara') depends on `IMissionProgressionService` from slice 'Missions'. — DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:31
- `CharaController` (slice 'Chara') depends on `IPaymentService` from slice 'Shop'. — DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:32
- `CharaService` (slice 'Chara') depends on `IMissionProgressionService` from slice 'Missions'. — DragaliaAPI/DragaliaAPI/Features/Chara/CharaService.cs:15
- `ClearPartyService` (slice 'ClearParty') depends on `IDungeonRepository` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/ClearParty/ClearPartyService.cs:17
- `HeroParamService` (slice 'CoOp') depends on `IDungeonRepository` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:18
- `HeroParamService` (slice 'CoOp') depends on `IBonusService` from slice 'Fort'. — DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:20
- `HeroParamService` (slice 'CoOp') depends on `WeaponHelper` from slice 'Weapons'. — DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:115
- `UpdateController` (slice 'Configuration') depends on `IFortService` from slice 'Fort'. — DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:23
- `UpdateController` (slice 'Configuration') depends on `IEmblemRepository` from slice 'Emblem'. — DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:24
- `UpdateController` (slice 'Configuration') depends on `FriendService` from slice 'Friends'. — DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:25
- `DmodeController` (slice 'Dmode') depends on `IStoryRepository` from slice 'Story'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeController.cs:15
- `DmodeController` (slice 'Dmode') depends on `IStoryService` from slice 'Story'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeController.cs:17
- `DmodeService` (slice 'Dmode') depends on `IDmodeCacheService` from slice 'DmodeDungeon'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:18
- `DmodeService` (slice 'Dmode') depends on `IPaymentService` from slice 'Shop'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:20
- `DmodeService` (slice 'Dmode') depends on `DmodeHelper` from slice 'DmodeDungeon'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:199
- `DmodeService` (slice 'Dmode') depends on `TalismanHelper` from slice 'DmodeDungeon'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:345
- `DmodeSkipResetAction` (slice 'Dmode') depends on `IDailyResetAction` from slice 'Login'. — DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeSkipResetAction.cs:8
- `DmodeDungeonService` (slice 'DmodeDungeon') depends on `IDmodeRepository` from slice 'Dmode'. — DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:18
- `DmodeDungeonService` (slice 'DmodeDungeon') depends on `IDmodeService` from slice 'Dmode'. — DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:20
- `DragonService` (slice 'Dragons') depends on `IStoryRepository` from slice 'Story'. — DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:25
- `DragonService` (slice 'Dragons') depends on `IPaymentService` from slice 'Shop'. — DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:27
- `DragonService` (slice 'Dragons') depends on `IMissionProgressionService` from slice 'Missions'. — DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:29
- `DungeonController` (slice 'Dungeon') depends on `IQuestService` from slice 'Quest'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonController.cs:16
- `DungeonController` (slice 'Dungeon') depends on `IMatchingService` from slice 'CoOp'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonController.cs:19
- `EventDropService` (slice 'Dungeon') depends on `IEventRepository` from slice 'Event'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:15
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IDungeonService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:14
- `FeatureExtensions` (slice 'AbilityCrests') depends on `DungeonService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:14
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IDungeonStartService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:15
- `FeatureExtensions` (slice 'AbilityCrests') depends on `DungeonStartService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:15
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IDungeonRepository` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:16
- `FeatureExtensions` (slice 'AbilityCrests') depends on `DungeonRepository` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:16
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IQuestEnemyService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:17
- `FeatureExtensions` (slice 'AbilityCrests') depends on `QuestEnemyService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:17
- `FeatureExtensions` (slice 'AbilityCrests') depends on `IOddsInfoService` from slice 'Dungeon'. — DragaliaAPI/DragaliaAPI/Features/Dungeon/FeatureExtensions.cs:18
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
- Access here is not default-deny: `HeroParamController.GetHeroParam` is in a controller that declares no authorization (on itself, a base controller or any action) while 62 sibling controllers do, and no fallback policy, global AuthorizeFilter or gated MapControllers covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. (×2) — REDACTED:17, REDACTED:23
- Access here is not default-deny: `MaintenanceController.GetText` is in a controller that declares no authorization (on itself, a base controller or any action) while 62 sibling controllers do, and no fallback policy, global AuthorizeFilter or gated MapControllers covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:14
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
ED5 · Idempotency
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — DragaliaAPI/DragaliaAPI.Test.Utils/StubPlayerIdentityService.cs:12, DragaliaAPI/DragaliaAPI.Test.Utils/StubPlayerIdentityService.cs:15, DragaliaAPI/DragaliaAPI/Infrastructure/Linq2Db/Json.cs:55
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `Value` is a shipped member whose body only throws — and it is REACHED: DragaliaAPI/DragaliaAPI/Features/Web/TimeAttack/TimeAttackService.cs:115 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — DragaliaAPI/DragaliaAPI/Infrastructure/Linq2Db/Json.cs:55
- The arm `EventKindType.Collect` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:141
- The arm `EventKindType.ExHunter` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:143
- The arm `EventKindType.Simple` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:144
- The arm `EventKindType.BattleRoyal` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:145
- The catch-all arm (reached by `None`, `LimitFall`, `DefeatAllEnemies`, `MaxTeamSize` and 27 more) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Dungeon/QuestCompletionService.cs:359
- The section `case SummonTickets.TenfoldSummonLimited:` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Shared/Reward/Handlers/SummonTicketHandler.cs:37
- The branch `if (shopType is ShopType.Special)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Shop/ShopService.cs:98
- The catch-all arm (reached by `DungeonMode`) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — DragaliaAPI/DragaliaAPI/Features/Story/StoryService.cs:64
- A test is skipped ("Test fails but functionality works") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×3) — DragaliaAPI/DragaliaAPI.Integration.Test/Other/MetricsTest.cs:19, PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:22, PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:82
- 9 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:588
- 8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:598
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×9) — DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:968, DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:969, DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:977, …
- `PickDistinct`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — DragaliaAPI/DragaliaAPI/Features/Dungeon/SingleValuePicker.cs:18
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- `pnpm run lint:prettier` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:50
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P2 · Observability
- Only 7/8 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 8, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P3 · Security & performance tooling
What to do
- The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `services.AddHttpClient<IBaasApi, BaasApi>( (sp, client) => { IOptionsMonitor<...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — DragaliaAPI/DragaliaAPI/ServiceConfiguration.cs:136
- `services.AddHttpClient<IPhotonStateApi, PhotonStateApi>( (sp, client) => { IO...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — DragaliaAPI/DragaliaAPI/ServiceConfiguration.cs:147
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×2) — DragaliaAPI/DragaliaAPI/Program.cs:22, PhotonStateManager/DragaliaAPI.Photon.StateManager/Program.cs:8
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×2) — DragaliaAPI/DragaliaAPI/Program.cs:22, PhotonStateManager/DragaliaAPI.Photon.StateManager/Program.cs:8
- No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — DragaliaAPI/DragaliaAPI/Features/Web/WebAuthenticationHelper.cs:17
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
- Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `DragaliaApiMetrics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — DragaliaAPI/DragaliaAPI/Infrastructure/Metrics/DragaliaApiMetrics.cs:22
- `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 20). Every use of it in `PhotonStateManagerMetrics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — PhotonStateManager/DragaliaAPI.Photon.StateManager/PhotonStateManagerMetrics.cs:20
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation
- Only 211/762 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — Aspire/Dawnshard.ServiceDefaults/HealthCheckWriter.cs:11
- No CancellationToken parameter — this work can't be stopped early once started. (×38) — DragaliaAPI/DragaliaAPI.Database/Repositories/BaseRepository.cs:12, DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:42, DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:62, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×3) — PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:39, PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:41, PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:50
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- ~0.1 `!` suppressions per 1k syntax nodes — 111 suppression(s) across the 934061 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66.0 | Adequate — gated by D18 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 62.2 | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 70.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44.9 | Weak — gated by P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36.6 | Weak — gated by D28, D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 72.1 | Strong | Solid. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 36 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 189 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half measured 53.7%; the JavaScript/TypeScript half could not be measured — MaintenanceWorker/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (11 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 95 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI.Integration.Test/Features/Maintenance/MaintenanceTest.cs:10
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI.Shared/MasterAsset/MasterAssetGroup.cs:67
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI/Features/Dungeon/OddsInfoService.cs:8
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI/Features/Login/Auth/SessionService.cs:22
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI/Features/Login/Auth/SessionService.cs:23
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI/Infrastructure/Serialization/MessagePack/InputOutputFormatters.cs:16
- WriteOnlyPrivateField DragaliaAPI/DragaliaAPI/Infrastructure/Serialization/MessagePack/InputOutputFormatters.cs:37
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle DragaliaAPI/DragaliaAPI.Database/Entities/Abstract/DbPlayerData.cs:5
- Namespace dependency cycle DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge DragaliaAPI/DragaliaAPI/Features/Parties/PartyPowerService.cs:1
- Orphaned knowledge DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:1
- <input> without a programmatic label Website/src/routes/(main)/admin/impersonation/+page.svelte:72
- <button> with no accessible text Website/src/routes/(main)/header.svelte:61
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unfinished stub — throws NotImplementedException DragaliaAPI/DragaliaAPI/Infrastructure/Linq2Db/Json.cs:55
Serious — 420 finding(s)
- TodoComment DragaliaAPI/DragaliaAPI.Database/Entities/DbPlayerBannerData.cs:47
- TodoComment DragaliaAPI/DragaliaAPI.Database/Factories/DbPlayerBannerDataFactory.cs:12
- TodoComment DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:53
- TodoComment DragaliaAPI/DragaliaAPI.Database/Repositories/PartyRepository.cs:46
- TodoComment DragaliaAPI/DragaliaAPI.Integration.Test/Features/Summoning/SummonTest.cs:557
- TodoComment DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/QuestDrops/QuestBonusReward.cs:7
- TodoComment DragaliaAPI/DragaliaAPI.Test/Features/Tool/SessionServiceTest.cs:13
- TodoComment DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:89
- TodoComment DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:215
- TodoComment DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:341
- TodoComment DragaliaAPI/DragaliaAPI/Features/Chara/CharaService.cs:26
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:636
- TodoComment DragaliaAPI/DragaliaAPI/Features/CoOp/Stamps/StampService.cs:24
- TodoComment DragaliaAPI/DragaliaAPI/Features/CoOp/Stamps/StampService.cs:40
- TodoComment REDACTED:14
- TodoComment DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:70
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dungeon/QuestCompletionService.cs:275
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dungeon/QuestCompletionService.cs:280
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dungeon/Skip/DungeonSkipController.cs:238
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dungeon/Skip/DungeonSkipController.cs:240
- TodoComment DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:188
- TodoComment DragaliaAPI/DragaliaAPI/Features/Present/PresentController.cs:95
- TodoComment DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:132
- TodoComment DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:981
- TodoComment DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:239
- Dead code: ModuleInitializer DragaliaAPI/DragaliaAPI.Database.Test/ModuleInitializer.cs:7
- Dead code: DbPlayerBannerDataFactory DragaliaAPI/DragaliaAPI.Database/Factories/DbPlayerBannerDataFactory.cs:5
- Dead code: DeleteQuests DragaliaAPI/DragaliaAPI.Database/Repositories/IQuestRepository.cs:9
- Dead code: GetMultipleViewerData DragaliaAPI/DragaliaAPI.Database/Repositories/IUserDataRepository.cs:21
- Dead code: ConvertIntToFlagList DragaliaAPI/DragaliaAPI.Database/Utils/TutorialFlagUtil.cs:41
- Dead code: ModuleInitializer DragaliaAPI/DragaliaAPI.Shared.SourceGenerator.Test/ModuleInitializer.cs:5
- Dead code: ModuleInitializer DragaliaAPI/DragaliaAPI.Shared.Test/ModuleInitializer.cs:6
- Dead code: ToPaymentType DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/EntityTypes.cs:58
- Dead code: GetFormattedText DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/AbilityData.cs:17
- Dead code: ObsoleteReasons DragaliaAPI/DragaliaAPI.Shared/ObsoleteReasons.cs:3
- Dead code: ModuleInitializer DragaliaAPI/DragaliaAPI.Test/ModuleInitializer.cs:7
- Dead code: TestData DragaliaAPI/DragaliaAPI.Test/TestData.cs:6
- Dead code: NextEnum DragaliaAPI/DragaliaAPI/Extensions/RandomExtensions.cs:7
- Dead code: DmodeSkipResetAction DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeSkipResetAction.cs:7
- Dead code: RemoveItemQuantityAsync DragaliaAPI/DragaliaAPI/Features/Event/IEventRepository.cs:37
- Dead code: DailySummoningDealResetAction DragaliaAPI/DragaliaAPI/Features/Login/Actions/DailySummoningDealResetAction.cs:9
- Dead code: DragonGiftResetAction DragaliaAPI/DragaliaAPI/Features/Login/Actions/DragonGiftResetAction.cs:11
- Dead code: ItemSummonResetAction DragaliaAPI/DragaliaAPI/Features/Login/Actions/ItemSummonResetAction.cs:6
- Dead code: LoginGiftResetAction DragaliaAPI/DragaliaAPI/Features/Login/Actions/LoginGiftResetAction.cs:9
- Dead code: LoadSessionIdToken DragaliaAPI/DragaliaAPI/Features/Login/Auth/ISessionService.cs:34
- Dead code: V10Update DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V10Update.cs:8
- Dead code: V11Update DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V11Update.cs:9
- Dead code: V12Update DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V12Update.cs:12
- Dead code: V15Update DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V15Update.cs:7
- Dead code: V26Update DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V26Update.cs:15
- Cross-slice coupling: AbilityCrests → Missions DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:20
- Cross-slice coupling: AbilityCrests → Tutorial DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:21
- Cross-slice coupling: AbilityCrests → Tutorial DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestService.cs:68
- Cross-slice coupling: AbilityCrests → Album DragaliaAPI/DragaliaAPI/Features/Album/FeatureExtensions.cs:10
- Cross-slice coupling: AbilityCrests → Album DragaliaAPI/DragaliaAPI/Features/Album/FeatureExtensions.cs:10
- Cross-slice coupling: Chara → Story DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:28
- Cross-slice coupling: Chara → Missions DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:31
- Cross-slice coupling: Chara → Shop DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:32
- Cross-slice coupling: Chara → Missions DragaliaAPI/DragaliaAPI/Features/Chara/CharaService.cs:15
- Cross-slice coupling: ClearParty → Dungeon DragaliaAPI/DragaliaAPI/Features/ClearParty/ClearPartyService.cs:17
- Cross-slice coupling: CoOp → Dungeon DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:18
- Cross-slice coupling: CoOp → Fort DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:20
- Cross-slice coupling: CoOp → Weapons DragaliaAPI/DragaliaAPI/Features/CoOp/HeroParamService.cs:115
- Cross-slice coupling: Configuration → Fort DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:23
- Cross-slice coupling: Configuration → Emblem DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:24
- Cross-slice coupling: Configuration → Friends DragaliaAPI/DragaliaAPI/Features/Configuration/UpdateController.cs:25
- Cross-slice coupling: Dmode → Story DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeController.cs:15
- Cross-slice coupling: Dmode → Story DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeController.cs:17
- Cross-slice coupling: Dmode → DmodeDungeon DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:18
- Cross-slice coupling: Dmode → Shop DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:20
- Cross-slice coupling: Dmode → DmodeDungeon DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:199
- Cross-slice coupling: Dmode → DmodeDungeon DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:345
- Cross-slice coupling: Dmode → Login DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeSkipResetAction.cs:8
- Cross-slice coupling: DmodeDungeon → Dmode DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:18
- Cross-slice coupling: DmodeDungeon → Dmode DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:20
- Async method without CancellationToken: WriteResponse Aspire/Dawnshard.ServiceDefaults/HealthCheckWriter.cs:11
- Async method without CancellationToken: SaveChangesAsync DragaliaAPI/DragaliaAPI.Database/Repositories/BaseRepository.cs:12
- Async method without CancellationToken: UpdateQuantity DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:42
- Async method without CancellationToken: FindAsync DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:62
- Async method without CancellationToken: UpdateQuantity DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:80
- Async method without CancellationToken: UpdateQuantity DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:90
- Async method without CancellationToken: GetMaterial DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:100
- Async method without CancellationToken: CheckQuantity DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:108
- Async method without CancellationToken: CheckQuantity DragaliaAPI/DragaliaAPI.Database/Repositories/InventoryRepository.cs:111
- Async method without CancellationToken: SetParty DragaliaAPI/DragaliaAPI.Database/Repositories/PartyRepository.cs:44
- Async method without CancellationToken: UpdatePartyName DragaliaAPI/DragaliaAPI.Database/Repositories/PartyRepository.cs:61
- Async method without CancellationToken: FindQuestAsync DragaliaAPI/DragaliaAPI.Database/Repositories/QuestRepository.cs:18
- Async method without CancellationToken: GetQuestDataAsync DragaliaAPI/DragaliaAPI.Database/Repositories/QuestRepository.cs:23
- Async method without CancellationToken: FindQuestEventAsync DragaliaAPI/DragaliaAPI.Database/Repositories/QuestRepository.cs:34
- Async method without CancellationToken: GetQuestEventAsync DragaliaAPI/DragaliaAPI.Database/Repositories/QuestRepository.cs:39
- Async method without CancellationToken: DeleteQuests DragaliaAPI/DragaliaAPI.Database/Repositories/QuestRepository.cs:49
- Async method without CancellationToken: FindCharaAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:37
- Async method without CancellationToken: FindDragonAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:45
- Async method without CancellationToken: FindDragonReliabilityAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:50
- Async method without CancellationToken: FindTalismanAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:58
- Async method without CancellationToken: FindWeaponBodyAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:63
- Async method without CancellationToken: GetCharaSetData DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:68
- Async method without CancellationToken: GetCharaSets DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:99
- Async method without CancellationToken: RemoveDragons DragaliaAPI/DragaliaAPI.Database/Repositories/UnitRepository.cs:137
- Async method without CancellationToken: GetUserDataAsync DragaliaAPI/DragaliaAPI.Database/Repositories/UserDataRepository.cs:32
- MethodTooLong: QuestHelper.QuestHelper(…) PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/GameLogic/QuestHelper.Data.cs:49
- MethodTooLong: UpdateDataService.MapUpdateDataList DragaliaAPI/DragaliaAPI/Features/Shared/UpdateDataService.cs:56
- MethodTooLong: SavefileService.Import DragaliaAPI/DragaliaAPI/Features/Login/Savefile/SavefileService.cs:97
- MethodTooLong: CharaController.CharaManaNodeUnlock DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:508
- MethodTooLong: MissionInitialProgressionService.GetInitialMissionProgress DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:56
- MethodTooLong: MappingExtensions.ProjectToHelperProjection DragaliaAPI/DragaliaAPI/Features/Friends/MappingExtensions.cs:40
- MethodTooLong: ClearPartyService.ProcessLostUnitList DragaliaAPI/DragaliaAPI/Features/ClearParty/ClearPartyService.cs:138
- MethodTooLong: DungeonRepository.BuildDetailedPartyUnit DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:277
- MethodTooLong: PaymentService.ProcessPayment DragaliaAPI/DragaliaAPI/Features/Shop/PaymentService.cs:31
- MethodTooLong: DungeonRepository.BuildDetailedPartyUnit DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:149
- MethodTooLong: PartyPowerService.CalculateCharacterPower DragaliaAPI/DragaliaAPI/Features/Parties/PartyPowerService.cs:106
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode Aspire/Dawnshard.ServiceDefaults/Extensions.cs:25
- CommentedOutCode DragaliaAPI/DragaliaAPI/Features/Missions/MissionService.cs:351
- CommentedOutCode DragaliaAPI/DragaliaAPI/Infrastructure/CustomControllerFeatureProvider.cs:28
- CommentedOutCode DragaliaAPI/DragaliaAPI/Infrastructure/OutputCaching/RepeatedRequestPolicy.cs:66
- CommentedOutCode DragaliaAPI/DragaliaAPI.Integration.Test/Features/Login/LoginTest.cs:169
- CommentedOutCode DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:588
- CommentedOutCode DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:598
- CommentedOutCode DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:982
- ClassTooLong: StaticHelperDataService DragaliaAPI/DragaliaAPI/Features/Friends/StaticHelperDataService.cs
- ClassTooLong: V1Missions DragaliaAPI/DragaliaAPI.MissionDesigner/Missions/Drill/V1Missions.cs
- ClassTooLong: DmodeDungeonService DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs
- ClassTooLong: DragonService DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs
- ClassTooLong: CharaController DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs
- ClassTooLong: QuestHelper PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/GameLogic/QuestHelper.cs
- ClassTooLong: PartyPowerService DragaliaAPI/DragaliaAPI/Features/Parties/PartyPowerService.cs
- ClassTooLong: SummonService DragaliaAPI/DragaliaAPI/Features/Summoning/SummonService.cs
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:141
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:143
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:144
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:145
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Dungeon/QuestCompletionService.cs:359
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Shared/Reward/Handlers/SummonTicketHandler.cs:37
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Shop/ShopService.cs:98
- Unfinished branch — throws NotImplementedException DragaliaAPI/DragaliaAPI/Features/Story/StoryService.cs:64
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Integration.Test/Features/Dungeon/DungeonRecordTest.cs:13
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Integration.Test/Features/Missions/MissionTest.cs:12
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Integration.Test/Features/Weapons/WeaponBodyTest.cs:9
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Test/GlobalSuppressions.cs:3
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Test/GlobalSuppressions.cs:4
- BareSuppressMessage DragaliaAPI/DragaliaAPI.Test/GlobalSuppressions.cs:8
- FileTooLong: Friends/StaticHelperDataService.cs DragaliaAPI/DragaliaAPI/Features/Friends/StaticHelperDataService.cs
- FileTooLong: Drill/V1Missions.cs DragaliaAPI/DragaliaAPI.MissionDesigner/Missions/Drill/V1Missions.cs
- FileTooLong: Dragons/DragonService.cs DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs
- FileTooLong: DmodeDungeon/DmodeDungeonService.cs DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs
- FileTooLong: Chara/CharaController.cs DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs
- FileTooLong: Savefile/SavefileService.cs DragaliaAPI/DragaliaAPI/Features/Login/Savefile/SavefileService.cs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Event/EventService.cs:381
- Edited copy of a member (21 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:416
- Edited copy of a member (21 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Summoning/SummonOddsLogic.cs:398
- Edited copy of a member (21 corresponding lines) REDACTED:48
- Edited copy of a member (21 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Event/BuildEventController.cs:21
- Edited copy of a member (21 corresponding lines) PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/Discord/DiscordPlugin.cs:83
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore
- Prerelease dependency: OpenTelemetry.Instrumentation.EntityFrameworkCore
- Prerelease dependency: OpenTelemetry.Instrumentation.Process
- Prerelease dependency: OpenTelemetry.Instrumentation.StackExchangeRedis
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- BarePragmaDisable Aspire/Dawnshard.AppHost/Program.cs:7
- BarePragmaDisable Aspire/Dawnshard.AppHost/Program.cs:16
- BarePragmaDisable DragaliaAPI/DragaliaAPI/Program.cs:154
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: SessionService.cs ↔ SessionAuthenticationHandler.cs DragaliaAPI/DragaliaAPI/Features/Login/Auth/SessionService.cs:1
- Change coupling: SessionService.cs ↔ Program.cs DragaliaAPI/DragaliaAPI/Features/Login/Auth/SessionService.cs:1
- Change coupling: DragaliaControllerBase.cs ↔ Program.cs DragaliaAPI/DragaliaAPI/Infrastructure/DragaliaControllerBase.cs:1
- Edited copy of a member (10 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeController.cs:110
- Edited copy of a member (10 corresponding lines) PhotonStateManager/DragaliaAPI.Photon.StateManager/Models/RedisGame.cs:21
- Edited copy of a member (10 corresponding lines) PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/Discord/DiscordPlugin.cs:71
- Duplicated block (7 lines × 2) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:631
- Duplicated block (7 lines × 2) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:356
- Duplicated block (7 lines × 2) DragaliaAPI/DragaliaAPI/Features/Story/StoryService.cs:398
- Unfinished stub — throws NotImplementedException DragaliaAPI/DragaliaAPI.Test.Utils/StubPlayerIdentityService.cs:12
- Unfinished stub — throws NotImplementedException DragaliaAPI/DragaliaAPI.Test.Utils/StubPlayerIdentityService.cs:15
- Unfinished stub — throws NotImplementedException DragaliaAPI/DragaliaAPI/Infrastructure/Linq2Db/Json.cs:55
- Deprecated: Aspire.Hosting.NodeJs REDACTED:8
- Deprecated: @cloudflare/vitest-pool-workers REDACTED:7
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:541
- Edited copy of a member (19 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Parties/PartyPowerService.cs:61
- Edited copies of one member (3 members, 21+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:276
- Edited copies of one member (3 members, 21+ corresponding lines) PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/CollectionExtensions.cs:117
- Edited copy of a member (16 corresponding lines) DragaliaAPI/DragaliaAPI/Features/TimeAttack/Validation/CharaListValidator.cs:12
- Edited copy of a member (16 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Event/EventService.cs:432
- Edited copy of a member (25 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/Start/DungeonStartController.cs:31
- Edited copy of a member (25 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Fort/FortController.cs:192
- Edited copy of a member (15 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Shared/Reward/Handlers/HustleHammerHandler.cs:19
- Edited copy of a member (15 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Friends/FriendService.cs:173
- Edited copy of a member (18 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/AbilityLogic.cs:135
- Edited copy of a member (18 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/MissionController.cs:42
- Edited copy of a member (7 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/MissionProgressionService.cs:145
- Edited copy of a member (7 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Shared/Reward/Handlers/HustleHammerHandler.cs:36
- Duplicated block (18 lines × 2) DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/CharaData.cs:181
- Duplicated block (18 lines × 2) DragaliaAPI/DragaliaAPI/Features/Weapons/WeaponService.cs:182
- Duplicated block (15 lines × 2) DragaliaAPI/DragaliaAPI/Features/Dmode/DmodeService.cs:314
- Duplicated block (15 lines × 2) DragaliaAPI/DragaliaAPI/Features/Fort/BonusService.cs:125
- Duplicated block (16 lines × 2) DragaliaAPI/DragaliaAPI/Features/Wall/WallStartController.cs:37
- Duplicated block (16 lines × 2) DragaliaAPI/DragaliaAPI/Infrastructure/Middleware/PhotonAuthenticationHandler.cs:83
- Duplicated block (8 lines × 2) DragaliaAPI/DragaliaAPI.Database/Entities/DbPlayerPresent.cs:24
- Duplicated block (8 lines × 2) REDACTED:112
- Duplicated block (9 lines × 2) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:428
- Duplicated block (9 lines × 2) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:104
- Outbound HTTP without resilience DragaliaAPI/DragaliaAPI/ServiceConfiguration.cs:136
- Outbound HTTP without resilience DragaliaAPI/DragaliaAPI/ServiceConfiguration.cs:147
- Disposable created and abandoned in the method that made it DragaliaAPI/DragaliaAPI/Infrastructure/Metrics/DragaliaApiMetrics.cs:22
- Disposable created and abandoned in the method that made it PhotonStateManager/DragaliaAPI.Photon.StateManager/PhotonStateManagerMetrics.cs:20
- Page without a main landmark MaintenanceWorker/src/web/page.html:2
- Animation without a prefers-reduced-motion guard Website/src/lib/shadcn/components/ui/sonner/sonner.svelte:20
- Stateful shared instance: Banner DragaliaAPI/DragaliaAPI/Features/Summoning/SummonBannerOptions.cs:53
- No data-protection/encryption
- UpdateDataService.MapUpdateDataList (cyclomatic 52) DragaliaAPI/DragaliaAPI/Features/Shared/UpdateDataService.cs:56
- MissionInitialProgressionService.GetInitialMissionProgress (cyclomatic 49) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:56
- CharaController.CharaManaNodeUnlock (cyclomatic 42) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:508
- PaymentService.ProcessPayment (cyclomatic 36) DragaliaAPI/DragaliaAPI/Features/Shop/PaymentService.cs:31
- ClearPartyService.ProcessLostUnitList (cyclomatic 22) DragaliaAPI/DragaliaAPI/Features/ClearParty/ClearPartyService.cs:138
- DungeonRepository.BuildDetailedPartyUnit (cyclomatic 22) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:277
- MissionProgressionService.ProcessMissionEvents (cyclomatic 20) DragaliaAPI/DragaliaAPI/Features/Missions/MissionProgressionService.cs:313
- WeaponService.TryBuildupGeneric (cyclomatic 19) DragaliaAPI/DragaliaAPI/Features/Weapons/WeaponService.cs:151
- DragonService.DragonLevelUp (cyclomatic 18) DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:628
- DmodeDungeonService.GenerateOddsInfo (cyclomatic 17) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:643
- DmodeDungeonService.GenerateSubsequentFloor (cyclomatic 16) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:447
- DmodeDungeonService.GenerateEnemies (cyclomatic 16) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:969
- FortService.CollectIncome (cyclomatic 16) DragaliaAPI/DragaliaAPI/Features/Fort/FortService.cs:95
- Repeated repair: DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:21
- CoverageExclusion DragaliaAPI/DragaliaAPI.Database/DatabaseConfiguration.cs:51
- XxxComment DragaliaAPI/DragaliaAPI/Features/Event/Summon/EventSummonService.cs:194
- DeadPreprocessorBranch DragaliaAPI/DragaliaAPI/Features/Fort/BonusService.cs:2
- ObsoleteWithCallers DragaliaAPI/DragaliaAPI/Features/Fort/FortRepository.cs:19
- HackComment DragaliaAPI/DragaliaAPI/Features/Login/LoginController.cs:75
- FixmeComment DragaliaAPI/DragaliaAPI/Features/Present/PresentController.cs:103
- Build failed
- CharaController.CharaManaNodeUnlock (cognitive 71) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:508
- ClearPartyService.ProcessLostUnitList (cognitive 37) DragaliaAPI/DragaliaAPI/Features/ClearParty/ClearPartyService.cs:138
- MissionProgressionService.ProcessMissionEvents (cognitive 37) DragaliaAPI/DragaliaAPI/Features/Missions/MissionProgressionService.cs:313
- FortService.CollectIncome (cognitive 26) DragaliaAPI/DragaliaAPI/Features/Fort/FortService.cs:95
- DmodeDungeonService.GenerateSubsequentFloor (cognitive 24) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:447
- DmodeDungeonService.GenerateEnemies (cognitive 24) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:969
- SavefileService.Import (cognitive 24) DragaliaAPI/DragaliaAPI/Features/Login/Savefile/SavefileService.cs:97
- UpdateDataService.MapUpdateDataList (cognitive 24) DragaliaAPI/DragaliaAPI/Features/Shared/UpdateDataService.cs:56
- DungeonRepository.BuildDetailedPartyUnit (cognitive 22) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:277
- StoryService.ReadQuestStory (cognitive 21) DragaliaAPI/DragaliaAPI/Features/Story/StoryService.cs:196
- EventDropService.ProcessEventPassiveDrops (cognitive 20) DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:21
- EventSummonService.ExecuteBoxSummon (cognitive 20) DragaliaAPI/DragaliaAPI/Features/Event/Summon/EventSummonService.cs:79
- StorySkipService.ProcessQuestCompletions (cognitive 20) DragaliaAPI/DragaliaAPI/Features/Story/Skip/StorySkipService.cs:119
- DragonService.IncreaseDragonReliability (cognitive 19) DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:75
- DragonService.GrantRewardDataForLevel (cognitive 19) DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:190
- DragonService.DragonLevelUp (cognitive 19) DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:628
- CharaController.LimitBreakChara (cognitive 18) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:444
- DungeonRepository.BuildDetailedPartyUnit (cognitive 18) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:149
- V9Update.Apply (cognitive 18) DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V9Update.cs:25
- PaymentService.ProcessPayment (cognitive 18) DragaliaAPI/DragaliaAPI/Features/Shop/PaymentService.cs:31
- ShopService.DoPurchase (cognitive 18) DragaliaAPI/DragaliaAPI/Features/Shop/ShopService.cs:23
- EventService.CreateEventData (cognitive 17) DragaliaAPI/DragaliaAPI/Features/Event/EventService.cs:169
- WeaponService.TryBuildupGeneric (cognitive 17) DragaliaAPI/DragaliaAPI/Features/Weapons/WeaponService.cs:151
- DungeonRepository.BuildDetailedPartyUnit (cognitive 16) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:25
- LoginService.RewardLoginBonus (cognitive 16) DragaliaAPI/DragaliaAPI/Features/Login/LoginService.cs:27
- SummonService.CommitSummonResult (cognitive 16) DragaliaAPI/DragaliaAPI/Features/Summoning/SummonService.cs:396
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 120+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/DungeonRepository.cs:28
- Edited copy of a member (44 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/Start/DungeonStartController.cs:62
- Edited copies of one member (3 members, 37+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Fort/BonusService.cs:106
- Edited copy of a member (30 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/MissionService.cs:124
- Edited copy of a member (38 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:154
- Edited copy of a member (36 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/Skip/DungeonSkipController.cs:100
- Edited copy of a member (26 corresponding lines) DragaliaAPI/DragaliaAPI.Database/Utils/CharaUtils.cs:15
- Edited copy of a member (33 corresponding lines) DragaliaAPI/DragaliaAPI/Features/AbilityCrests/AbilityCrestController.cs:58
- Edited copy of a member (37 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Wall/WallStartController.cs:25
- Edited copies of one member (3 members, 30+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Dungeon/EventDropService.cs:315
- Edited copy of a member (24 corresponding lines) DragaliaAPI/DragaliaAPI.Shared/MasterAsset/MasterAssetData.cs:116
- Edited copies of one member (3 members, 17+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDeveloperController.cs:21
- Edited copy of a member (22 corresponding lines) DragaliaAPI/DragaliaAPI/Features/DmodeDungeon/DmodeDungeonService.cs:824
- Edited copies of one member (3 members, 18+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:200
- Edited copies of one member (7 members, 12+ corresponding lines) DragaliaAPI/DragaliaAPI/Features/Missions/MissionController.cs:160
- Edited copies of one member (5 members, 15+ corresponding lines) PhotonStateManager/DragaliaAPI.Photon.StateManager/Controllers/EventController.cs:153
- Edited copy of a member (13 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Fort/FortService.cs:617
- Edited copy of a member (12 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Trade/AbilityCrestTradeController.cs:38
- Edited copy of a member (14 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Event/EventService.cs:492
- Edited copy of a member (6 corresponding lines) DragaliaAPI/DragaliaAPI.Database/Entities/DbPlayerFriendRequest.cs:25
- Edited copy of a member (8 corresponding lines) DragaliaAPI/DragaliaAPI/Features/Story/StoryService.cs:397
- Duplicated block (35 lines × 2) DragaliaAPI/DragaliaAPI/Features/Dungeon/Start/DungeonStartController.cs:71
- Duplicated block (27 lines × 2) DragaliaAPI/DragaliaAPI.Database/Entities/DbPlayerPresent.cs:34
- Duplicated block (19 lines × 2) DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/AbilityCrestBuildupGroup.cs:13
- Duplicated block (14 lines × 2) DragaliaAPI/DragaliaAPI/Features/Summoning/SummonOddsLogic.cs:122
- Duplicated block (13–14 lines × 2) DragaliaAPI/DragaliaAPI/Features/Missions/InitialProgress/MissionInitialProgressionService.cs:544
- Duplicated block (10 lines × 2) DragaliaAPI/DragaliaAPI/Features/Chara/CharaController.cs:613
- Duplicated block (5 lines × 2) DragaliaAPI/DragaliaAPI.Database/Utils/CharaConstants.cs:8
- Duplicated block (17 lines × 2) PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/Discord/DiscordPlugin.cs:34
- Coverage not measured — JavaScript/TypeScript suite
- CI formatting step cannot fail REDACTED:50
- No DR/backup evidence
Minor — 81 finding(s)
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Album/CharaHonorHelper.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Player/UserService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Shop/ShopService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Database/Utils/DragonConstants.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Chara/CharaService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Dragons/DragonController.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Shared/PlayerDetails/PlayerIdentityService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/Missions/MissionCompleteType.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/ManaCircle/CharaLimitBreak.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Shop/ItemSummonService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/Shop/IShop.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Album/AlbumService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Database/Utils/TutorialFlagUtil.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/QuestRewards/QuestRewardData.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V22Update.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Item/ItemService.cs:1
- Orphaned file DragaliaAPI/DragaliaAPI/Features/Login/SavefileUpdate/V4Update.cs:1
- Commented-out code DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:588
- Commented-out code DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/Materials.cs:598
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:968
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:969
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:977
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dragons/DragonService.cs:978
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dungeon/OddsInfoService.cs:24
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Dungeon/OddsInfoService.cs:37
- Commented-out code DragaliaAPI/DragaliaAPI/Features/Summoning/SummonService.cs:670
- Commented-out code DragaliaAPI/DragaliaAPI/Infrastructure/CustomControllerFeatureProvider.cs:30
- Commented-out code DragaliaAPI/DragaliaAPI/Infrastructure/OutputCaching/RepeatedRequestPolicy.cs:68
- Fat interface: IUnitRepository (17 members) DragaliaAPI/DragaliaAPI.Database/Repositories/IUnitRepository.cs:6
- Fat interface: IShop (37 members) DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/Shop/IShop.cs:5
- Fat interface: IEventRepository (21 members) DragaliaAPI/DragaliaAPI/Features/Event/IEventRepository.cs:5
- Fat interface: IEventService (17 members) DragaliaAPI/DragaliaAPI/Features/Event/IEventService.cs:5
- Fat interface: IFortService (19 members) DragaliaAPI/DragaliaAPI/Features/Fort/IFortService.cs:7
- Fat interface: IMissionProgressionService (29 members) DragaliaAPI/DragaliaAPI/Features/Missions/IMissionProgressionService.cs:6
- Duplicated predicate DragaliaAPI/DragaliaAPI.Shared/MasterAsset/Models/QuestData.cs:62
- Duplicated predicate DragaliaAPI/DragaliaAPI/Features/TimeAttack/Validation/CharaListValidator.cs:21
- Duplicated predicate Website/src/routes/(main)/account/+layout.ts:13
- Duplicated predicate DragaliaAPI/DragaliaAPI/Features/Friends/FriendNotificationService.cs:58
- Duplicated predicate DragaliaAPI/DragaliaAPI/Features/Friends/FriendNotificationService.cs:28
- Duplicated predicate DragaliaAPI/DragaliaAPI/Features/Friends/FriendService.cs:249
- Endpoints outside the guard REDACTED:17
- Endpoints outside the guard REDACTED:23
- Endpoints outside the guard REDACTED:14
- REDACTED
- REDACTED
- REDACTED
- Disabled test DragaliaAPI/DragaliaAPI.Integration.Test/Other/MetricsTest.cs:19
- Disabled test PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:22
- Disabled test PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:82
- No security response headers detected
- No security response headers detected DragaliaAPI/DragaliaAPI/Program.cs:22
- No security response headers detected PhotonStateManager/DragaliaAPI.Photon.StateManager/Program.cs:8
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected DragaliaAPI/DragaliaAPI/Program.cs:22
- No app-layer HTTPS enforcement detected PhotonStateManager/DragaliaAPI.Photon.StateManager/Program.cs:8
- Interpolated log message defeats structured logging PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:39
- Interpolated log message defeats structured logging PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:41
- Interpolated log message defeats structured logging PhotonPlugin/DragaliaAPI.Photon.Plugin/Shared/Helpers/PluginHostExtensions.cs:50
- ObsoleteWithoutCallers DragaliaAPI/DragaliaAPI/Features/Shared/IUpdateDataService.cs:7
- ObsoleteWithoutCallers DragaliaAPI/DragaliaAPI/Features/Shared/UpdateDataService.cs:32
- Projects may be oversized for their cohesion DragaliaAPI/DragaliaAPI/DragaliaAPI.csproj:1
- Projects may be oversized for their cohesion DragaliaAPI/DragaliaAPI.Shared/DragaliaAPI.Shared.csproj:1
- REDACTED
- REDACTED
- Partial data-retention evidence
- No ADRs found REDACTED:4
- `AttackBaseOnHPUpRate` spells `HP` where 22 names in the project spell it `Hp` DragaliaAPI/DragaliaAPI.Shared/Definitions/Enums/AbilityTypes.cs:72
- redundant comment DragaliaAPI/DragaliaAPI.Integration.Test/Features/Trade/TreasureTradeResetTest.cs:13
- Split DragaliaAPI.Shared DragaliaAPI/DragaliaAPI.Shared/DragaliaAPI.Shared.csproj:1
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- Member throws NotSupportedException DragaliaAPI/DragaliaAPI/Features/Dungeon/SingleValuePicker.cs:18
- No ADRs
- Logging is not universal
- No changelog
- Secure cookie flags not detected DragaliaAPI/DragaliaAPI/Features/Web/WebAuthenticationHelper.cs:17
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 61 finding(s)
- Outdated: Aspire.Hosting.AppHost
- Outdated: Aspire.Hosting.PostgreSQL
- Outdated: Aspire.Hosting.Redis
- Outdated: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Outdated: OpenTelemetry.Extensions.Hosting
- Outdated: OpenTelemetry.Instrumentation.AspNetCore
- Outdated: OpenTelemetry.Instrumentation.Http
- Outdated: OpenTelemetry.Instrumentation.Runtime
- Outdated: FluentAssertions
- Outdated: Microsoft.EntityFrameworkCore.InMemory
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Microsoft.Extensions.TimeProvider.Testing
- Outdated: MockQueryable.EntityFrameworkCore
- Outdated: MockQueryable.Moq
- Outdated: Moq
- Outdated: xunit.v3.mtp-v2
- Outdated: Microsoft.CodeAnalysis.CSharp
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Npgsql.EntityFrameworkCore.PostgreSQL
- Outdated: Microsoft.AspNetCore.Mvc.Testing
- Outdated: Microsoft.AspNetCore.TestHost
- Outdated: Microsoft.Extensions.Diagnostics.Testing
- doc comments repeat the names DragaliaAPI/DragaliaAPI/Features/AbilityCrests/IAbilityCrestRepository.cs:19
- doc comments repeat the names DragaliaAPI/DragaliaAPI.Database/Entities/DbNewsItem.cs:54
- doc comments repeat the names DragaliaAPI/DragaliaAPI.Integration.Test/Features/AbilityCrests/AbilityCrestTest.cs:9
- doc comments repeat the names PhotonPlugin/DragaliaAPI.Photon.Plugin/Plugins/GameLogic/GameLogicPlugin.cs:439
- doc comments repeat the names Shared/DragaliaAPI.Photon.Shared/Models/ApiGame.cs:46
- doc comments repeat the names PhotonStateManager/DragaliaAPI.Photon.StateManager/Controllers/GetController.cs:67
- doc comments repeat the names DragaliaAPI/DragaliaAPI.Shared/MasterAsset/MasterAssetData.cs:36
- doc comments repeat the names DragaliaAPI/DragaliaAPI.Test/UnitTestUtils.cs:22
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: NSubstitute
- Mock framework: Moq
- Mock framework: NSubstitute
- Skipped (documented): ExportSave_CounterIncreased DragaliaAPI/DragaliaAPI.Integration.Test/Other/MetricsTest.cs:19
- Skipped (documented): CreateRoom_CounterIncreases PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:22
- Skipped (documented): CloseRoom_CounterDecreases PhotonStateManager/DragaliaAPI.Photon.StateManager.Test/Other/MetricsTest.cs:82
- Off the main sequence: DragaliaAPI.Photon.Shared Shared/DragaliaAPI.Photon.Shared/DragaliaAPI.Photon.Shared.csproj:1
- Off the main sequence: DragaliaAPI.Shared DragaliaAPI/DragaliaAPI.Shared/DragaliaAPI.Shared.csproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-de8a4cef0d9b476eba0ec262d83c053c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-de8a4cef0d9b476eba0ec262d83c053c/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=422" --report-format json --report-path /tmp/watchdog-gitleaks-de8a4cef0d9b476eba0ec262d83c053c/history-2.json --exit-code 0 --source . | 10 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-de8a4cef0d9b476eba0ec262d83c053c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude DragaliaAPI/DragaliaAPI.Database/Migrations --exclude DragaliaAPI/DragaliaAPI.Shared/Generated --exclude Website/src/lib/shadcn . | 73 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list DragaliaAPI.slnx package --vulnerable --include-transitive --format json | 21 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 189 file(s) — `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/EventIdAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/MissionTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Models/Attributes/WallTypeAttribute.cs`, `DragaliaAPI/DragaliaAPI.MissionDesigner/Program.cs`, `DragaliaAPI/DragaliaAPI.Shared.SourceGenerator/EquatableReadOnlyList.cs`, … (+184 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Email — 1 field(s)
- AtgenNAccountInfo.Email DragaliaAPI/DragaliaAPI/Models/Generated/Components.cs:3512