@elyx-code/project-logic-tree 0.0.6935 → 0.0.6936

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.ts CHANGED
@@ -9882,9 +9882,22 @@ export declare enum BaseValueDescriptorIds {
9882
9882
 
9883
9883
  /**
9884
9884
  * Checks whether two data-type entities are compatible.
9885
- * Order matters. In places where one data-type is constrained and the other is not,
9886
- * the first data-type (dataTypeA) is considered the value writer (source).
9887
- * while the second data-type (dataTypeB) is considered the value reader (target).
9885
+ *
9886
+ * Order matters. `dataTypeA` is treated as the value writer (source) and
9887
+ * `dataTypeB` as the value reader (target). `compatible: true` means every
9888
+ * possible value of A is acceptable to B (i.e. A ⊆ B). `exact: true`
9889
+ * additionally means A and B describe the same value set (A ≡ B).
9890
+ *
9891
+ * Notable behaviour:
9892
+ * - `null` represents an unconstrained data-type. An unconstrained side is
9893
+ * considered compatible with anything (lenient codebase convention).
9894
+ * - Degenerate single-child or/and-group wrappers (e.g. `[string]`,
9895
+ * `and[string]`) are transparently collapsed to their child as long as
9896
+ * the wrapper hasn't overridden `isList`/`asType`. So `string` and
9897
+ * `[string]` compare exactly equivalent.
9898
+ * - For or-groups, A is compatible with B iff every option of A fits in B
9899
+ * (any option of B if B itself is an or-group). The function does NOT
9900
+ * return `compatible: true` just because some single pair overlaps.
9888
9901
  *
9889
9902
  * @param dataTypeA
9890
9903
  * @param dataTypeB