edfcore 0.3.115 → 0.3.116

package/CHANGELOG.md

@@ -6,6 +6,13 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.3.116
+
+- **Fixed** two reference tables calling `EdfSignal.physicalDimension` "exactly as written". It is
+  `trimEdfField(raw.physicalDimension)`, the same treatment `label`, `transducerType` and
+  `prefiltering` get — and those neighbouring rows already say "trimmed", so the table singled this
+  field out as the one that is not.
+
 ## 0.3.115
 
 - **Fixed** the two TAL-level diagnostics whose `raw` was not the bytes their `byteOffset` and

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.3.115";
+export declare const VERSION = "0.3.116";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.115';
+export const VERSION = '0.3.116';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.3.115",
+  "version": "0.3.116",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.115';
+export const VERSION = '0.3.116';