@cosyte/astm 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 0.1.4
+
+### Patch Changes
+
+- f471127: The documentation of `AstmMessage.classification` now says what it has always done: it classifies the whole parsed stream, not one message, so a `Q` in any message of a multi-message stream makes the whole stream read as a host query. To classify one message, call `classifyMessage(m.records)` on each message from `messages()`.
+
+  The type documentation of `AstmMessageClassification`, `AstmMessageKind`, `QueryRecord`, `UnsupportedRecord`, `classifyMessage` and `ASTM_RECORD_AMBIGUOUS_MESSAGE_KIND` says the same, and that warning's message text now reads "Stream carried both" rather than "Message carried both", because a `Q` in one message and an `R` in another raise it too. Classification, warning codes and every other value are unchanged.
+
+## 0.1.3
+
+### Patch Changes
+
+- fbebdf2: Checking whether a result value is numeric, the check behind the units-absent warning, now takes time linear in the value's length; a value padded with a long run of spaces held the parser for seconds (about 3.5 at 50,000 spaces), and the time grew with the square of the run.
+
+  Every value is classified exactly as before, so the same results warn.
+
 ## 0.1.2
 
 ### Patch Changes

package/dist/index.cjs

@@ -620,9 +620,12 @@ var WARNING_CODES = {
    */
   ASTM_RECORD_UNINTERPRETED_QUERY_STATUS: "ASTM_RECORD_UNINTERPRETED_QUERY_STATUS",
   /**
-   * A message carried **both** a `Q` (request) and an `R` (result) record: a contradictory shape. The
-   * message is classified `host-query` (the `Q` **dominates**, so it is never read as a result set) and
+   * The stream carried **both** a `Q` (request) and an `R` (result) record: a contradictory shape. The
+   * stream is classified `host-query` (the `Q` **dominates**, so it is never read as a result set) and
    * this warning flags the anomaly. Positional context only; no field value.
+   *
+   * Classification is folded over the whole stream, so a `Q` in one message and an `R` in another
+   * raise it too. `classifyMessage(m.records)` over `messages()` says which message carried which.
    */
   ASTM_RECORD_AMBIGUOUS_MESSAGE_KIND: "ASTM_RECORD_AMBIGUOUS_MESSAGE_KIND",
   /**
@@ -810,7 +813,7 @@ function uninterpretedQueryStatus(position) {
 function ambiguousMessageKind(position) {
   return {
     code: WARNING_CODES.ASTM_RECORD_AMBIGUOUS_MESSAGE_KIND,
-    message: "Message carried both a Q (request) and an R (result) record, classified host-query; Q dominates.",
+    message: "Stream carried both a Q (request) and an R (result) record, classified host-query; Q dominates.",
     position
   };
 }
@@ -1938,7 +1941,7 @@ function parseDateField(raw, recordIndex, recordType, fieldIndex, warnings) {
   return date;
 }
 function isNumericValue(value) {
-  return /^\s*[<>]?\s*-?\d+(?:\.\d+)?\s*$/u.test(value);
+  return /^\s*(?:[<>]\s*)?-?\d+(?:\.\d+)?\s*$/u.test(value);
 }
 function fieldRaw(field) {
   return field !== void 0 && field.raw.length > 0 ? field.raw : void 0;
@@ -3144,7 +3147,7 @@ function concatBytes3(chunks) {
 }
 
 // src/index.ts
-var VERSION = "0.1.2";
+var VERSION = "0.1.4";
 
 exports.ABNORMAL_FLAG_CODES = ABNORMAL_FLAG_CODES;
 exports.ABNORMAL_FLAG_VOCABULARY = ABNORMAL_FLAG_VOCABULARY;