jbrowse-plugin-msaview 3.3.0 → 3.4.0

package/dist/MsaViewPanel/util.d.ts

@@ -1,3 +1,21 @@
+/**
+ * Whether `querySeqName` names a row this alignment actually has.
+ *
+ * react-msaview's `seqPosToGlobalCol` answers 0 for a name it does not know, so
+ * without this every genome position maps to the first column and hovering the
+ * genome — or a connected structure — lights column 0 of an unrelated row. The
+ * name is wrong more often than it looks: it defaults to `QUERY`, which an
+ * uploaded alignment has no reason to carry, and the manual panel leaves it
+ * empty when it cannot match the protein to a row.
+ *
+ * The other direction has no such hole: msaCoordToGenomeRegions needs the query
+ * row's sequence to map a column at all, so a missing row is already nothing
+ * there.
+ */
+export declare function hasQueryRow(model: {
+    rows: string[][];
+    querySeqName: string;
+}): boolean;
 export declare function hasHoverPosition(hovered: unknown): hovered is {
     hoverPosition: {
         coord: number;

package/dist/MsaViewPanel/util.js

@@ -1,3 +1,20 @@
+/**
+ * Whether `querySeqName` names a row this alignment actually has.
+ *
+ * react-msaview's `seqPosToGlobalCol` answers 0 for a name it does not know, so
+ * without this every genome position maps to the first column and hovering the
+ * genome — or a connected structure — lights column 0 of an unrelated row. The
+ * name is wrong more often than it looks: it defaults to `QUERY`, which an
+ * uploaded alignment has no reason to carry, and the manual panel leaves it
+ * empty when it cannot match the protein to a row.
+ *
+ * The other direction has no such hole: msaCoordToGenomeRegions needs the query
+ * row's sequence to map a column at all, so a missing row is already nothing
+ * there.
+ */
+export function hasQueryRow(model) {
+    return model.rows.some(r => r[0] === model.querySeqName);
+}
 export function hasHoverPosition(hovered) {
     return (!!hovered &&
         typeof hovered === 'object' &&