Deactivate strain menu items for genes without strain tree #1137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requirements
Description
In conjunction with eg-web-common PR 166, this pull request would deactivate strain-level homology menu items for genes lacking a strain-level gene tree.
A gene can have inferred strain homologies even if it lacks an inferred gene tree within the strain dataset. For example, if a strain gene-trees pipeline assigns a gene to a cluster containing only genes that are in the default collection, the cluster may be deleted from the strain gene-tree dataset, though homologies may have been inferred between its gene members in the default gene-trees pipeline.
In these cases, the homologies may be available through both the default and strain-level menu items. As the strain-level homology view is redundant with the default homology view, deactivating its menu item will not necessarily negatively impact the accessibility of the relevant homology data.
Views affected
This change would affect homology views for a subset of genes in strain gene-tree collections:
Examples:
Because the Barley pangenome is the preferred gene-tree collection for this species, its strain-level menu items are unaffected by the changes in this pull request.
Possible complications
None expected.
Merge conflicts
None detected.
Related JIRA Issues (EBI developers only)
N/A