shacl-wasm-node 0.1.10 → 0.2.0

package/README.md

@@ -92,9 +92,24 @@ validator.validateText(text, format, base, inference)     // inference: "none" (
 validator.shapeCount                                      // shapes compiled
 
 const { validateTurtle } = require('./pkg-node/shacl_wasm.js');
-validateTurtle(shapesTurtle, dataTurtle, base);           // one-shot, no reuse
+validateTurtle(dataTurtle, shapesTurtle, base);           // one-shot, no reuse
+validateTurtle(selfDescribingTurtle);                     // shapes carried by the data
 ```
 
+**The one-shot takes `(data, shapes)`, and took `(shapes, data)` before 0.2.0.**
+Data comes first in every other surface — the Python `validate(data, shapes)`,
+the CLI's `--data`/`--shapes`, and the Rust API under all of them — and this
+was the only one reversed. Omitting `shapes` validates a self-describing
+document against the shapes it carries, as the other two also do.
+
+Transposing them used to be a silent fault rather than a loud one: the data
+graph compiled as a shapes graph, declared no shapes, and validating against no
+shapes conforms — so the caller was told their graph was valid when nothing had
+been checked. A shapes graph with no shapes now throws instead, which is what
+makes the reordering safe: code written for the old signature fails rather than
+passing. `Validator.fromTurtle` stays permissive, since it exposes
+`shapeCount` for a caller who wants to decide for themselves.
+
 `inference: "rdfs"` validates against the RDFS closure of the data, so a finding
 can depend on an entailed `rdf:type` rather than only an asserted one.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "shacl-wasm-node",
   "description": "WebAssembly bindings for the shacl validation engine (CommonJS, for Node and require())",
-  "version": "0.1.10",
+  "version": "0.2.0",
   "license": "MIT OR Apache-2.0",
   "repository": {
     "type": "git",

package/shacl_wasm.d.ts

@@ -90,5 +90,17 @@ export function start(): void;
 /**
  * One-shot validation, for a caller with a single data graph that gains
  * nothing from holding a compiled [`Validator`].
+ *
+ * `data` comes first, and `shapes` may be omitted for a self-describing
+ * document that carries its own — the same call shape as the Python binding's
+ * `validate(data, shapes=None)`, the CLI's `--data`/`--shapes`, and the Rust
+ * `validate(data, shapes_graph, ..)` underneath all of them.
+ *
+ * It used to take `(shapes, data)`, alone among the four. Transposing the two
+ * is not a loud mistake but a quiet one: the data graph compiles as a shapes
+ * graph, declares no shapes, and validating anything against no shapes
+ * conforms. The caller is told their graph is valid when nothing was checked.
+ * Hence the guard below, which is what makes this reordering safe to make —
+ * a call written for the old signature now fails instead of passing.
  */
-export function validateTurtle(shapes: string, data: string, base?: string | null): Report;
+export function validateTurtle(data: string, shapes?: string | null, base?: string | null): Report;

package/shacl_wasm.js

@@ -261,18 +261,30 @@ exports.start = start;
 /**
  * One-shot validation, for a caller with a single data graph that gains
  * nothing from holding a compiled [`Validator`].
- * @param {string} shapes
+ *
+ * `data` comes first, and `shapes` may be omitted for a self-describing
+ * document that carries its own — the same call shape as the Python binding's
+ * `validate(data, shapes=None)`, the CLI's `--data`/`--shapes`, and the Rust
+ * `validate(data, shapes_graph, ..)` underneath all of them.
+ *
+ * It used to take `(shapes, data)`, alone among the four. Transposing the two
+ * is not a loud mistake but a quiet one: the data graph compiles as a shapes
+ * graph, declares no shapes, and validating anything against no shapes
+ * conforms. The caller is told their graph is valid when nothing was checked.
+ * Hence the guard below, which is what makes this reordering safe to make —
+ * a call written for the old signature now fails instead of passing.
  * @param {string} data
+ * @param {string | null} [shapes]
  * @param {string | null} [base]
  * @returns {Report}
  */
-function validateTurtle(shapes, data, base) {
+function validateTurtle(data, shapes, base) {
     try {
         const retptr = wasm.__wbindgen_add_to_stack_pointer(-16);
-        const ptr0 = passStringToWasm0(shapes, wasm.__wbindgen_export, wasm.__wbindgen_export2);
+        const ptr0 = passStringToWasm0(data, wasm.__wbindgen_export, wasm.__wbindgen_export2);
         const len0 = WASM_VECTOR_LEN;
-        const ptr1 = passStringToWasm0(data, wasm.__wbindgen_export, wasm.__wbindgen_export2);
-        const len1 = WASM_VECTOR_LEN;
+        var ptr1 = isLikeNone(shapes) ? 0 : passStringToWasm0(shapes, wasm.__wbindgen_export, wasm.__wbindgen_export2);
+        var len1 = WASM_VECTOR_LEN;
         var ptr2 = isLikeNone(base) ? 0 : passStringToWasm0(base, wasm.__wbindgen_export, wasm.__wbindgen_export2);
         var len2 = WASM_VECTOR_LEN;
         wasm.validateTurtle(retptr, ptr0, len0, ptr1, len1, ptr2, len2);