ref data into data II/V #118
Open
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
blaggacao
force-pushed
the
ref-data-into-data
branch
2 times, most recently
from
470b9b5
to
af599b6
Compare
- preparation for a more view based data access
blaggacao
force-pushed
the
ref-data-into-data
branch
from
af599b6
to
c99adbd
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.
This PR contains the commit of a previous PR
since its cumulative in nature.
Only the second commit is meant for scrutiny.
By placing (internal) data structures into their
own module, we will have an easier time (in future
PRs) to reason about a single internal state
for each deployment into which we can provide
useful views for each action.