@suss/extractor 0.29.0 → 0.31.0

package/dist/index.d.cts

@@ -1888,13 +1888,14 @@ declare function valueToReadFurtherFrom<T>(reading: Reading<T>): T | null;
  * composeWrappers.ts: what a unit does once the code registered around
  * it is folded in.
  *
- * A wrapper is a meta-function: it takes a unit and returns a unit. Its
- * summary already says what it does, because the call to its
- * continuation comes through as a `delegate` transition, so one
- * application is the wrapper's short circuits plus its pass-throughs
- * times the wrapped unit's transitions, and a stack is repeated
- * application. The package README works the example through and says
- * what composition does not read.
+ * A wrapper is a meta-function: it takes a unit and returns a unit. The
+ * call to its continuation comes through as a `delegate` transition, so
+ * a path that ends before that call is a response the caller gets
+ * instead of the unit's own, and a path that reaches it hands the
+ * request on without responding. The responses go beside the unit's own
+ * outcomes and the pass-throughs go nowhere, because the unit's
+ * outcomes already say what happens on them. The package README works
+ * the example through and says what composition does not read.
  */
 
 /**
@@ -3402,6 +3403,9 @@ interface RawCodeStructure {
     /** Fragment spreads in `graphqlDocument` with no definition in it, so a
      * partially read document is marked rather than passed off as whole. */
     graphqlUnresolvedFragments?: string[];
+    /** Spreads in `graphqlDocument` the project defines more than once, with
+     * different bodies, so no definition of them could be used. */
+    graphqlAmbiguousFragments?: string[];
     /** Set when a document reference was recognized but its body could not be
      * read, so an unreadable document is accounted for instead of dropped. */
     graphqlUnresolvedDocument?: {

package/dist/index.d.ts

@@ -1888,13 +1888,14 @@ declare function valueToReadFurtherFrom<T>(reading: Reading<T>): T | null;
  * composeWrappers.ts: what a unit does once the code registered around
  * it is folded in.
  *
- * A wrapper is a meta-function: it takes a unit and returns a unit. Its
- * summary already says what it does, because the call to its
- * continuation comes through as a `delegate` transition, so one
- * application is the wrapper's short circuits plus its pass-throughs
- * times the wrapped unit's transitions, and a stack is repeated
- * application. The package README works the example through and says
- * what composition does not read.
+ * A wrapper is a meta-function: it takes a unit and returns a unit. The
+ * call to its continuation comes through as a `delegate` transition, so
+ * a path that ends before that call is a response the caller gets
+ * instead of the unit's own, and a path that reaches it hands the
+ * request on without responding. The responses go beside the unit's own
+ * outcomes and the pass-throughs go nowhere, because the unit's
+ * outcomes already say what happens on them. The package README works
+ * the example through and says what composition does not read.
  */
 
 /**
@@ -3402,6 +3403,9 @@ interface RawCodeStructure {
     /** Fragment spreads in `graphqlDocument` with no definition in it, so a
      * partially read document is marked rather than passed off as whole. */
     graphqlUnresolvedFragments?: string[];
+    /** Spreads in `graphqlDocument` the project defines more than once, with
+     * different bodies, so no definition of them could be used. */
+    graphqlAmbiguousFragments?: string[];
     /** Set when a document reference was recognized but its body could not be
      * read, so an unreadable document is accounted for instead of dropped. */
     graphqlUnresolvedDocument?: {