Rearchitect client project structure #451
Merged
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.
Description
This PR addresses something I've been wanting to do for the client source for a while to help the project structure and cohesion between type/interface definitions and the components that use them.
The component modules have been rename/reorged so similar components are groups together. I also moved most of the the type definitions to the component module instead of just having them float out in a separate
types
module on their own for use by any component. This should make it a little easier to identify when a interface is being shared by too many things and may be violating the single responsibility principle (for example, thercraSite
schema is a suspect candidate).So a lot of moving stuff around to where things should have been originally but nothing really changing.
Issue ticket number and link
Checklist