ref(server): Organize project services in nested modules #4139
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.
Organizing all the
project_*.rs
files we have in theservices/
module in a module structure.This only moves files around, no functional changes. It is a preparation to split out more of the convoluted services into smaller digestible parts. For example, the
project_cache.rs
module contains a lot of utility and helper types not relevant for the service itself, it should be possible to split this out eventually.I chose
projects
as the base module to avoid having aproject/project/
module, also I think it makes sense, it manages all projects and the nested module just represents a single project.#skip-changelog