-
Notifications
You must be signed in to change notification settings - Fork 286
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
Modify fetch resources from single study to multi-study #5038
Modify fetch resources from single study to multi-study #5038
Conversation
✅ Deploy Preview for cbioportalfrontend ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
projection: 'DETAILED', | ||
} | ||
// Fetch resource data for each studyId, then return combined results | ||
const allResources = _(studyIds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the js array natively has map on it so you don't need to wrap in lodash here. this might seem confusing given what i said last week but the real message is that we should strive to use the semantically accurate and descriptive method. if it's just map, then no reason to use lodash. the other reason to use lodash is it's support for chaining, but we're not doing that here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay no problem I can change to the native map. I was just going off of what the previous author did in another function in this same file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's working from product perspective, thanks @hweej !
Fix cBioPortal/cbioportal#11158. Add multiy-study result for files & resource tab on Study view. Fetch resource data for each study on the frontend and combine the results. Note: in the future we might want to improve the endpoint to handle multiple studies directly