Skip to content

Bump to 1.34.0: a project's labels and run order read as MATLAB writes them - #60

Merged
ww-mw merged 2 commits into
mainfrom
bump-1.34.0
Oct 2, 2026
Merged

ww-mw merged 2 commits into
mainfrom
bump-1.34.0

Conversation

@ww-mw

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

Copy link
Copy Markdown
Member

Releases the three project-parser fixes from #59:

  • ReadOnly is read by its per-element vocabulary, so a label the user added is no longer drawn as one of MATLAB's built-ins.
  • A hook whose first entry carries no Extension (what a freshly built project writes) is no longer listed in reverse run order.
  • The label catalog and the working folders come back in a stable order rather than the store's, which differed per layout.

Carries one extra commit: two facts about the corpus trees that project_truth.json does not record — FixedPathMultiFile is the layout a new project gets, and the conversion does not recurse into referenced projects.

ww-mw added 2 commits October 2, 2026 12:07
Two facts that are in the fixtures rather than in project_truth.json:
FixedPathMultiFile is the layout a NEW project gets — parityLib is never
converted and is in it — so convertDefinitionFiles is the opt-out rather than
the opt-in, and that layout is the shape most .prj files in the wild are in.
And the conversion does not recurse into referenced projects: each format's
parityLib keeps its own .prj and its own fixedPathV2 store, which is why a Toml
project can hold a reference to an XML one.
@ww-mw
ww-mw merged commit c360da1 into main Oct 2, 2026
4 checks passed
@ww-mw
ww-mw deleted the bump-1.34.0 branch October 2, 2026 16:09
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