You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like I've done for the Vehicle Destroy and Vehicle Character Death logics, move the calculation logic into a singlar class so we can easily re-use it across both Instance and Global Aggregates. Right now, we're duplicating the exact same logic across both, the only difference being their destination, the same documents are created, which is inefficent.
Additionally, should the logic need to be tweaked, we would have to do it to both, which is a maintainability issue.
The text was updated successfully, but these errors were encountered:
Maelstromeous
changed the title
Refactor: Move duplicated logic into Logic Classes
Refactor: Move duplicated Aggregator calculation logic into Logic Classes
Oct 12, 2020
Like I've done for the Vehicle Destroy and Vehicle Character Death logics, move the calculation logic into a singlar class so we can easily re-use it across both Instance and Global Aggregates. Right now, we're duplicating the exact same logic across both, the only difference being their destination, the same documents are created, which is inefficent.
Additionally, should the logic need to be tweaked, we would have to do it to both, which is a maintainability issue.
The text was updated successfully, but these errors were encountered: