You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the main table will load 100 rows of data and handle the pagination in the front-end, this can be moved to the graphql query to save on data transfer.
Make a new ticket in api repo with info above
---- need a results object to return total
---- 1 layer of nesting for all hits (entities ex file + runs+ analysis)
Keep the existing GraphQL; add a new v2 path https://api.rdpc-qa.cancercollaboratory.org/v1/graphql
Can switch over services to /v1 one by one [workflow node, workflow ui, workflow management, workflow graph, aggregator, model-tee]
Update this section in UI as well; may need to reach out to @lepsalex for aggregation endpoints.
Currently the main table will load 100 rows of data and handle the pagination in the front-end, this can be moved to the graphql query to save on data transfer.
Use the standard GraphQL pagination model: https://graphql.org/learn/pagination/. We donts need full hits/edges/node
Make a new ticket in api repo with info above
---- need a results object to return total
---- 1 layer of nesting for all hits (entities ex file + runs+ analysis)
Keep the existing GraphQL; add a new v2 path
https://api.rdpc-qa.cancercollaboratory.org/v1/graphql
Can switch over services to
/v1
one by one [workflow node, workflow ui, workflow management, workflow graph, aggregator, model-tee]Update this section in UI as well; may need to reach out to @lepsalex for aggregation endpoints.
Specs:
https://wiki.oicr.on.ca/display/icgcargotech/RDPC+Gateway+Design#RDPCGatewayDesign-PaginationSchema
The text was updated successfully, but these errors were encountered: