Refactor HydeKernel code to organized single-used traits #429
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.
While I'm generally a bit weary of single-use traits (I love them, but feel that they can be a sign that the code needs to be split up into more classes), the HydeKernel is a vital part of the framework and cannot really be split up the same way as other classes can.
This PR moves logic to scoped internal traits in the Foundation\Concerns namespace. This will make it easier to get an overview of what's going on in each domain. This does not affect any of the logic itself or end usage of the framework, just how it is internally structured.