the custom resolver should also add cancer type and cancer type detailed to sample model
apollo client and dashboard can then access these additional pieces of data as if they are part of the regular sample model (i.e., use built in filtering, etc. on CT/CTdetailed)
Notes on implementation
We'll go with 1 for now and be ok with the 20s+ wait time until we implement samples caching.
Solution option
Effort level
Initial loading time
Challenges
1. Use GraphQL's built-in solution (OGM)
Very low
20s+
Long loading time. In the resolver we're using the OGM to query all samples then manually sort them with Javascript
2. Side step GraphQL via a direct Neo4j query
High
5s
We'll lose out on all GraphQL benefits and have to maintain a robust Neo4j query builder. This will add extra complexity for future dev related to Samples views
3. Hybrid: use #2 only for the initial page load, #1 for searching
Medium
Another idea: use OGM to query and sort data for records from the latest 6 months or some other time range.
Further improve rendering time by eliminating excessive renders related to the RecordsList component.
Notes from meeting
Notes on implementation
We'll go with 1 for now and be ok with the 20s+ wait time until we implement samples caching.
Another idea: use OGM to query and sort data for records from the latest 6 months or some other time range.
Further improve rendering time by eliminating excessive renders related to the
RecordsList
component.