-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapt app to syncronizer #719
Conversation
# Conflicts: # tests/NexusMods.StandardGameLocators.TestHelpers/StubbedGames/StubbedGame.cs
# Conflicts: # src/NexusMods.DataModel/Games/AGame.cs
Codecov Report
@@ Coverage Diff @@
## main #719 +/- ##
==========================================
- Coverage 64.86% 61.95% -2.91%
==========================================
Files 660 674 +14
Lines 19395 19500 +105
Branches 1293 1276 -17
==========================================
- Hits 12580 12082 -498
- Misses 6489 7090 +601
- Partials 326 328 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
src/NexusMods.DataModel/LoadoutSynchronizer/ALoadoutSynchronizer.cs
Outdated
Show resolved
Hide resolved
src/NexusMods.DataModel/LoadoutSynchronizer/FlattenedToLoadoutTransformer.cs
Outdated
Show resolved
Hide resolved
src/Games/NexusMods.Games.BethesdaGameStudios/BethesdaLoadoutSynchronizer.cs
Show resolved
Hide resolved
As reported on Discord, running the |
Qodana for .NET60 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Code should be clearer with latest changes.
If you want there are a few miscellaneous warnings, but otherwise this can be merged for me.
Reworks the app to use the new ALoadoutSyncronizer, and for each game to have a default syncronizer. Reworks the Skyrim code to reference this synchronizer and updates the tests accordingly
LoadoutMarker is now a singleton for each LoadoutId and the LoadoutRegistry will automatically update the DataStoreIds whenever the loadout is altered. This is in preparation for the next step of tech debt removal where we'll be going single process with the app. So the round-trip and the incured latency of hitting the database is no longer needed, making these markers singletons reduces a bit of complexity in the design.