@jbrowse/core 5.0.0-beta.10 → 5.0.0-beta.13

package/esm/util/featureTransforms.d.ts

@@ -5,19 +5,20 @@ import type { Feature } from './simpleFeature.ts';
 export { BIN_OVERLAP_FIELD, DEFAULT_BIN_AS } from './stepTables.ts';
 export declare const DEFAULT_BIN_FIELD = "start";
 export declare const DEFAULT_FLATTEN_FIELD = "subfeatures";
-export declare const DEFAULT_CELLS_FIELD = "seq";
+export { DEFAULT_CELLS_FIELD } from './cellsStep.ts';
 export declare const DEFAULT_COVERAGE_AS = "coverage";
 export declare const DEFAULT_PILEUP_AS = "row";
 export declare const DEFAULT_PILEUP_FIELDS: [string, string];
 /**
  * #api
  * How a record states its other end, or undefined where it states none: the
- * `mate` a paired adapter fills (BEDPE, STAR-Fusion), or an `ALT` the breakend
- * and symbolic-SV readers resolve. The `mate` step admits exactly the features
- * this names one for, so a caller deciding whether links are the picture a
- * track wants asks here rather than re-reading the fields.
+ * `mate` a paired adapter fills (BEDPE, STAR-Fusion), an `ALT` the breakend
+ * and symbolic-SV readers resolve, or a read's `next_ref` and `next_pos`. The
+ * `mate` step admits exactly the features this names one for, so a caller
+ * deciding whether links are the picture a track wants asks here rather than
+ * re-reading the fields.
  */
-export declare function matedBy(f: Feature): "alt" | "mate" | undefined;
+export declare function matedBy(f: Feature): "alt" | "mate" | "pair" | undefined;
 /**
  * #api
  * One layer of a faceted request: its rows in section order, and the stacked