Skip to content

Pin core v1.36.1: a complex value inside an MCOS object shows as the number it is - #44

Merged
ww-mw merged 1 commit into
mainfrom
core-v1.36.1
Oct 9, 2026
Merged

ww-mw merged 1 commit into
mainfrom
core-v1.36.1

Conversation

@ww-mw

@ww-mw ww-mw commented Oct 9, 2026

Copy link
Copy Markdown
Member

What

This moves the core pin from v1.36.0 to v1.36.1 (mathworks/data-explorer-core#67, released as v1.36.1).

A complex property of an MCOS object showed [object Object]. For example, a Simulink.Parameter whose Value is 3+4i or [1+2i 3+4i 5+6i], in a .mat file or a model workspace. It now shows the number, spelled the way the extension spells complex numbers elsewhere. Also in this core release:

  • NaN/Inf parts and integer or single classes are kept;
  • the Property Inspector lays a complex matrix out as a matrix;
  • the binary and text .sldd writers now write complex values that MATLAB reads back as they were.

Only package.json and package-lock.json change. The extension's own version is not bumped.

Verification

  • npm run verify: 163 files, 3,106 tests passed.
  • npm run test:integration: 153 passing, 1 pending, the same as Pin core v1.36.0: an MCOS object nested in a struct or cell resolves as its top-level twin #42.
  • npm run check:leak: all 646 lockfile resolutions point at the public registry.
  • The installed core, run on the two files that first showed the bug, gives 3+4i and [1+2i 3+4i 5+6i], with no [object Object] on any node. On core's new complex fixtures, .mat, model-workspace, text .sldd and binary .sldd agree.

…number it is

Core v1.36.1 shows a complex property of an MCOS object (a Simulink.Parameter
whose Value is 3+4i or [1+2i 3+4i 5+6i], in a .mat file or a model workspace)
as the number, where it showed [object Object]. NaN/Inf parts and integer or
single classes are kept, the Property Inspector lays a complex matrix out as a
matrix, and the binary and text .sldd writers write complex values that MATLAB
reads back as they were.

The lock now resolves data-explorer-core to v1.36.1 (21a4ecd). Every lockfile
resolution still points at the public registry. The extension's own version is
not bumped here.
@ww-mw
ww-mw merged commit adaeb8d into main Oct 9, 2026
4 checks passed
@ww-mw
ww-mw deleted the core-v1.36.1 branch October 9, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant