Denormalize entity data #596
Draft
Conversation
This file contains 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
testower
force-pushed
the
denormalize-entity-data
branch
from
761501a to
f481798
Compare
…or denormalization
testower
force-pushed
the
denormalize-entity-data
branch
from
f481798 to
17a625a
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR will denormalize entity data, meaning system, vehicle types and pricing plans will be stored separately in redis, instead of being embedded in stations and vehicle entities. They will then have to be resolved in the graphql layer. This will prepare for simplification of the updaters for vehicles and stations, ultimately being based on delta calculations (#543).