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
use grch38 genome nexus for grch38 studies #3147
Conversation
c9909c1
to
80ca7aa
Compare
@@ -1623,4 +1648,37 @@ export class PatientViewPageStore { | |||
}, | |||
[] | |||
); | |||
|
|||
// if we use grch37(default), grch38GenomeNexusUrl will be undefined | |||
@computed get grch38GenomeNexusUrl() { |
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.
This value is serving as the "source of truth" of the current build. I don't think the name is abstract enough. It maybe that genome nexus is the only feature of the portal which is genome build dependent, but the fact that it's a property of studies suggests is something more general.
In other words, I'm a developer, i want to know what the current build is. I wouldn't think to check whether grch38GenomeNexusUrl is undefined. I would be looking for "currentReferenceGenemeBuild" or some such abstract property. It can contain the same logic here (based on study result).
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.
updated
@@ -3187,6 +3206,45 @@ export class ResultsViewPageStore { | |||
[] | |||
); | |||
|
|||
// if we use grch37(default), grch38GenomeNexusUrl will be undefined | |||
@computed get grch38GenomeNexusUrl() { |
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.
This is maybe out of the scope of this PR but we have a lot of "almost identical" code segments in our stores. It would be great if we can somehow unify these similar methods.
For this method though, it might be possible to move the logic into a utility function.
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.
@onursumer where would be a good place to move to?
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.
We have StoreUtils.ts
. We can maybe add a function there if we don't have a more specific utility 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.
typo in the function name
@leexgh so, MutationTable component should have a property, buildWhateverLink:(blah)=>string; This function will be called inside the column renderer for our column. We define the function ... maybe in ReusltsViewMutationMapper which has access to the store. |
src/shared/components/mutationTable/column/HgvsgColumnFormatter.tsx
Outdated
Show resolved
Hide resolved
src/pages/patientView/clinicalInformation/PatientViewPageStore.ts
Outdated
Show resolved
Hide resolved
e707ff7
to
e3f016c
Compare
src/pages/resultsView/mutation/ResultsViewMutationMapperStore.ts
Outdated
Show resolved
Hide resolved
src/pages/resultsView/mutation/ResultsViewMutationMapperStore.ts
Outdated
Show resolved
Hide resolved
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.
LGTM after @onursumer comments are addressed.
I made one minor comment about renaming a function
Fix: cBioPortal/cbioportal#7368
If the study has mutations based on grch38, use https://grch38.genomenexus.org
For now we won't support studies having both grch37 and grch38 mutation data. It will always use the grch37 genome nexus instance in that case.