Skip to content
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

Show Strain menu iff genome has strain gene trees #1038

Merged

Conversation

twalsh-ebi
Copy link
Contributor

Description

Some genomes that have strain metadata in their core database but are not in a strain-level gene-tree collection. Currently a Strains submenu is shown for these genomes, but this Strains submenu is unnecessary in such cases and could be removed.

This PR removes the Strains submenu in such cases.

Views affected

This affects the gene view of genomes that have strain metadata but are not in a strain-level gene-tree collection.

Here are some examples of such genomes. In these cases, a Strains menu is not needed:

For comparison, here are some examples of genomes in the Wheat cultivars protein-tree collection, for which a Strains menu is expected to appear:

Here are some further examples of genomes in the Pig breeds protein-tree collection, for which a Strains menu is expected to appear:

Possible complications

None expected.

Merge conflicts

None detected.

Related JIRA Issues (EBI developers only)

@shradhaebi
Copy link

Hi @imransl This looks fine to me. Thanks !

@jyothishnt
Copy link
Contributor

Is the sandbox still updated with this PR @twalsh-ebi ?

@jyothishnt
Copy link
Contributor

Merging as it needs to be in for 113. But please test it on rc.ensembl.org

@jyothishnt jyothishnt merged commit 2b676f3 into Ensembl:postreleasefix/113 Sep 24, 2024
jyothishnt added a commit that referenced this pull request Sep 24, 2024
* postreleasefix/113:
  Show Strain menu iff genome has strain gene trees (#1038)
jyothishnt added a commit that referenced this pull request Sep 24, 2024
* postreleasefix/113:
  Show Strain menu iff genome has strain gene trees (#1038)
@twalsh-ebi
Copy link
Contributor Author

My apologies @jyothishnt, I had moved things around when testing a different PR and had not moved things back in time for the review. In any case, it looks like the changes have been successful on the RC site. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants