-
Notifications
You must be signed in to change notification settings - Fork 233
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
Redirect the linkout endpoint "ln" to curated non-redundant list of studies #3335
Conversation
…quick select button config Signed-off-by: Adam Abeshouse <abeshoua@mskcc.org>
Signed-off-by: Adam Abeshouse <abeshoua@mskcc.org>
); | ||
if (curatedNonRedundantStudyIdsArray) { | ||
// filter out studies that user doesnt have access to | ||
const allStudies = await client.getAllStudiesUsingGET({}); |
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.
way to anticipate this. did you manage to test this?
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.
yeah, I caught this because there's actually one in the curated list that's not available in the public portal lol
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.
so, has that been failing?
@tmazor sorry i should have given you an opportunity to test it. @adamabeshouse could the discrepancy have something to do with the study that isn't actually publically accessible? |
Also, @tmazor @adamabeshouse i will check but i think the sample count on homepage comes from counts stored in studies table which are not kept in sync with dynamic counts. I will bring this up in standup |
@alisman Just to summarize what we said in stand-up, I don't think that's a factor because the full list is 179 studies, minus the non-accessible one is 178, which is the number we're seeing in those screenshots. @tmazor yes, I also thought it was weird to send to mutations, but that's actually the existing behavior in the code at least, regardless of the OQL. was it not doing that before? |
@adamabeshouse I don't think I'd ever used this ln?... link before, so I don't know what it did before. Maybe there's a historical reason why that behavior was desired? @jjgao do you know why the ln?... link goes to the Mutations tab? In principle I would prefer if it brought a user to Cancer Types Summary to be consistent with running a query from the homepage, but I don't really think it matters all that much so it's probably ok to leave as is. |
No description provided.