sysml-validate 0.15.7 → 0.15.8

package/out/main.js

@@ -61187,10 +61187,22 @@ ${baseIndent}}`;
   // target feature, so each end must be able to hold it (OMG SysML v2 Part 1
   // §7.12 ItemFlow / PayloadFeature). Reported per end, and only when the end
   // resolves unambiguously and carries exactly one written type.
+  //
+  // A MESSAGE is deliberately exempt, though the grammar folds it into the same
+  // statement. OMG SysML 8.2.2.16 gives `flow` FlowEndMembers — a FlowEnd is a
+  // FlowFeature, the feature that holds the payload — while a message's `from`
+  // and `to` are MessageEventMembers: `message m of i : I from evt1 to evt2` is
+  // "parsed as an abstract FlowUsage, but without any flowEnds", its two ends
+  // redefining Message::sourceEvent and Message::targetEvent (8.4.12.2). The
+  // ends of a message are the two OCCURRENCES that exchange the payload, so
+  // demanding that they be able to hold it reports every sequence-diagram
+  // message as an error.
   checkFlowPayload(decl, model, index, accept) {
     if (decl.$type !== "FlowStmt")
       return;
     const flow = decl;
+    if (flow.flowKind === "message")
+      return;
     const payload = flowPayloadType(flow.payload);
     if (!payload || payload.conjugated)
       return;
@@ -70012,7 +70024,7 @@ async function runValidation(command) {
 }
 
 // src/main.ts
-var VERSION2 = true ? "0.15.7" : "dev";
+var VERSION2 = true ? "0.15.8" : "dev";
 async function main(argv) {
   const command = parseArgs(argv);
   if (command.kind === "help") {