Split up sections of the codebase into dedicated projects#785
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #766
Refresh.Commonto share some simple common functionalityRefresh.Coreserves a similar purpose, but only for the context of the critical servers that need the full context/typing of what Refresh is. Projects that depend onRefresh.Coreare aware of the database and what levels are and such, whereas non-critical servers likeRefresh.HttpServeronly cares about routing traffic.Refresh.GameServerwill depend onRefresh.Core, and most things live there now. Instead, this project's role will be to "bring everything together".Refresh.Interfaces.Game,Refresh.Interface.APIv3, etc. to split up the codebase more cleanly.Refresh.GameServerdepends on these projects and discovers endpoints from these assemblies.