Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

narratives load sidecar files from cache; #1312

Merged

Conversation

eharkins
Copy link
Contributor

As James and I sketched out verbally
over the phone, this tries to set up
then functions for promises in the dataset
cache which are initiated at the start
of loading a narrative with sidecar files.
This has been minimally tested with
the frequencies file and seems to work
on the surface.

@jameshadfield here's what we discussed, needs more testing.

@eharkins eharkins requested a review from jameshadfield March 27, 2021 00:05
@jameshadfield jameshadfield temporarily deployed to auspice-bug-narratives--za7be3 March 27, 2021 00:05 Inactive
@eharkins eharkins changed the title narratives load freqs & root seq from cache; narratives load sidecar files from cache; Mar 30, 2021
@trvrb
Copy link
Member

trvrb commented Jul 4, 2021

Does this still need merging / review?

@eharkins eharkins force-pushed the bug-narratives-frequencies branch from 3c9d28c to 0db3a38 Compare August 6, 2021 19:15
@eharkins eharkins force-pushed the bug-narratives-frequencies-cache branch from fdec8ea to 821a116 Compare August 6, 2021 19:16
As James and I sketched out verbally
over the phone, this tries to set up
then functions for promises in the dataset
cache which are initiated at the start
of loading a narrative with sidecar files.
This has been minimally tested with
the frequencies file and seems to work
on the surface.
@eharkins eharkins force-pushed the bug-narratives-frequencies-cache branch from 821a116 to daea0d4 Compare August 6, 2021 19:17
@eharkins
Copy link
Contributor Author

eharkins commented Aug 6, 2021

Thanks Trevor for reminding me about this. It needs to probably just get merged into #1305 since it is on top of that larger PR which lacks this small but important piece. Then further review and testing is definitely needed on #1305 before we merge, which I am working on now but would also appreciate your feedback.

@eharkins eharkins merged commit d20e833 into bug-narratives-frequencies Aug 6, 2021
@eharkins eharkins deleted the bug-narratives-frequencies-cache branch August 6, 2021 19:44
jameshadfield added a commit that referenced this pull request Aug 11, 2021
These changes were motivated by
[#1283](#1283) which arose
as we used different code paths for loading a dataset viz and a
narrative.

Here we represent each dataset by a `Dataset` object. This is used for
stand alone datasets, each dataset in a tangletree, and each dataset in
a narrative. Each dataset instance describes the various API endpoints
of datafiles for each dataset, manages fetching of these datafiles and,
where appropriate, can dispatch data to update redux state.

This has been tested on various single datasets, tangle-trees, and
narratives in this repo. Notably, this commit breaks narratives with
multiple datasets; this will be fixed in a subsequent commit to
reflect Eli's work in PR #1312.
jameshadfield pushed a commit that referenced this pull request Aug 11, 2021
This complements the previous commit to allow narrative slide-changes to
change datasets by querying the cache set up at narrative load.
Appropriate sidecar files are also loaded, and we ensure that
sidecar data from the previous dataset is not displayed.

This work is based upon PR #1312 by eharkins.

Co-authored-by: eharkins <[email protected]>
jameshadfield pushed a commit that referenced this pull request Aug 11, 2021
This complements the previous commit to allow narrative slide-changes to
change datasets by querying the cache set up at narrative load.
Appropriate sidecar files are also loaded, and we ensure that
sidecar data from the previous dataset is not displayed.

This work is based upon PR #1312 by eharkins.

Co-authored-by: eharkins <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants