Refactor how data is shared by API, systems, and entities #193
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.
Describe what the PR does:
This PR is way larger than it should be, FYI, but it was necessary to accommodate the scope of the changes I wanted.
I recently came to the conclusion that the interdependencies between the API, the system, and the entity were a mess: copies of data were being shared all over the place, it wasn't clear which object was responsible for what, and I felt anxious every time I had to look at it. 😆 So, this PR unwinds things and makes data responsibilities clearer:
Does this fix a specific issue?
N/A
Checklist:
README.md
anddocs/
with any new documentation.AUTHORS.md
.