Skip to content

Releases

v0.44.0: fixes from audits 46 to 50

Choose a tag to compare

@github-actions github-actions released this 19 Nov 23:05
679af7d

Install: npm install umlimator@0.44.0, or "umlimator": "github:zintaen/umlimator#v0.44.0".

Audits 46 to 50 confirmed 103 findings: 1 high, 33 medium and 69 low. 98 are fixed in seven pull requests (#519, #520 and #521 for audit 46, then one per round: #535, #538, #540 and #543), each code fix with a test that fails without it; audit 50 finding 12 (the gallery's wording about the bike share) went with the bike share in #544. Audit 49 findings 13 to 16 (one medium, three low) are still open: the lane that fixed them was left out when #540 combined that round (Known gaps).

This release holds 24 pull requests since 0.43.0, #518 to #545 (#529 to #531 and #533 were combined into #535): besides the fixes, the map-repo pin (#518), describe() on map views (#525), map line weights (#536), the examples and the docs site's Examples page (#522 to #528, #532, #534, #537, #542, #544), the repository's community files (#539), the README's links (#541) and the CI gate (#545). bench/expected.json changes only because the bench's models changed (the bike share, then bench/models/i59.json in #544): no audit fix moves a hashed layout, the order-states and sales-classes examples are as 0.43.0 left them, and the stress views' crossing pins are unchanged.

The changes a host sees without editing anything: every map line is drawn at weight 1's width at rest, and a weight of 2 or 3 shows only on hover, selection and keyboard focus, with the line's what (or "weight 2 of 3") in its title and accessible name (#536, #543); describe(), paths() and reach() read a version-2 map view's own lines with their labels, steps and latency (#525); an edited line's dot is drawn off its label (#538); validate() warns on more (present-values, stereotype-text, comment-link in more views, a change mark not written in lower case) and no longer calls an interface realization from a component or a port an error (#535, #538, #540, #543); diff() says and marks edited, moved and re-owned members and writes a new diffMarks field on the typed views it lays out (#535, #540, #543); more editing gestures are refused where validate() would call the result an error (#521, #538, #543); the MCP tour tool refuses a tour the page cannot ride (#535, #538); and the bike share and the other retired example files are gone from examples/ (#527, #544), so a link to examples/bike-share.json, examples/bookshop.json or examples/bookshop.html, or to the Bookshop Atlas's api or checkout view, now breaks. What changes for callers:

  • Core and layout. A map line's weight shows only on hover, selection and keyboard focus (#536): at rest every line has weight 1's width and arrowhead; a line of weight 2 or 3 grows to its weight's width with its heavier arrowhead when the pointer is on it or on a card at either end, when it or a card at either end is selected, and when its line key has keyboard focus, and its title and accessible name add its what (all the whats of the edges it stands for, joined by " / "), else "weight 2 of 3" or "weight 3 of 3". Weight 1 lines say nothing new, and mindmap branches and typed lines are unchanged. describe(), paths() and reach() read a version-2 map view's own lines with their labels, steps and latency (#525): a view with no diagram, or diagram: "map", is walked as a map, where it was walked by model line, so describe() now says a line's label and step. At rest the flow line is trimmed for the weight 1 arrowhead, and a weighted line draws a second flow line (flowline fl-hv) for its heavy arrowhead that shows in the same states (#543, audit 50 finding 2). An edited line's dot is drawn on the longest stretch of the line clear of its label: in a sweep of the examples with every other line also marked edited, 46 of 84 dots sat under a label before and none do now (audit 48 finding 21; #538). svgOf() draws a map view whose container names itself, or another in a cycle, as its parent, where it overflowed the stack (#538). A map line or card change that is not text draws unmarked, as validate() and the typed views already read it (#519). lib/umlimator.d.ts and the schema now describe a map line's change as main draws it (added, new, removed, changed, modified, drawn with no style needed) and say it is written in lower case (#519, #535; audit 46 findings 6 and 24, audit 47 finding 4).
  • diff(), the diff page and stills. diff() says and marks edited members: a member in both models whose own fields or owner changed is marked changed and said by name ("renames charge to inlet in Battery"), and a retyped part's lost ports are drawn removed beside its new ones (audit 47 finding 1; #535, #543). A member moved to another owner is said once ("moves X out of A into B", no more "changes A (members)") and drawn back removed at its old place, under a fresh id <id>~moved (#540). An added or removed part, port or lane is marked, and a removed one is drawn back (#520). A new public field, view.diffMarks (marks by shape id and gone lines; in lib/umlimator.d.ts and the schema), carries what a typed view draws that is no element or line of its own: the old C4 implied line or SysML containment line of a re-owned element is drawn back removed (audit 47 findings 0 and 14; #535), a deleted container's implied line comes back removed (#543), and a shape drawn from what it reads (a C4 instance or implied line, an IDEF1X entity, an information flow, a class or package name qualified through an owner, an object, a parametric constraint property, a port typed by an interface block) is marked changed only when its drawing changes (#520, #535, #538, #540, #543). A C4 implied line that is new in the picture is marked added; one drawn before stays changed (audit 50 finding 0; #543). Relationships diff() brings back removed no longer join an implied line (#538). On a communication view the message rows carry their marks (audit 46 finding 9, high; #520) and number the live messages as the new model does (#538). An interaction overview's inline interaction marks its messages, lifelines and fragments, and is marked changed when its sequence view changes through its own lines (#520, #538, #540). An added or removed dashed typed line keeps its dash, and a solid one stays solid, so a removed call message draws solid rose (#520, #535). Timing constraints are marked and a removed one is drawn back (#540); a deleted BPMN group is drawn removed (#540); an IDEF1X entity whose only identifying relationship was removed is drawn independent (#535); a removed mindmap topic's branch is no longer drawn solid in its branch colour (#520). diff().views leaves out a view listed only through what it refers to or reads when its picture is the same before and after (#535), and lists again a C4 container view whose cards move when a context relationship to its subject is added or removed (audit 48 finding 0, a round 47 regression; #538), and lists a view whose card opens a retitled view when a map card shares that view's id (audit 48 finding 3; #538). The summary names a BPMN lane by its label (#535) and a removed extend's extension point by its name (#538).
  • validate() and rules. New warnings: present-values, a port side or interface present value the view ignores (component and composite views, #535; internal block and parametric views, #538); stereotype-text, a stereotype stored with its marks such as «entity», on any element (#535; the Stereotypes field now strips one pair); comment-link on the state machine and use case views (#521), judged on the lines they draw (#535), and on the activity (#535) and information flow views (#543); and "write it in lower case" for a change mark in another letter case, which still draws (#535). realization-target accepts a class, component, port, enumeration or data type realizing an interface (#540), so a component or port that realizes one is no longer an error. The warning on a sequence fragment operator that is not text now says so, and how it is drawn (#521). Validating a C4 deployment model is no longer quadratic (#519).
  • Page, keyboard and accessibility. A line's weight is explained in its title and accessible name, and its key's keyboard focus shows it (#536). A communication row's "Message N of M" counts live rows only (#538). The diff page's change words follow the marks above.
  • UML structural. A stereotype or metaclass dragged out of its profile is refused in every view, a type's own moveTo hook included (#521, #535). An interface realization from a component or a port is drawn and checked as the component view always did (#540). Composite structure: the ports on an added part are marked, the ports on a removed part are drawn removed (#520), and F2 or a member row on a part, port, role or collaboration use is linear in its spaces (64,000 spaces: 17 s before, under 250 ms now; #543).
  • UML behavioural. A comment link between two elements that are not comments is refused in the use case, state machine and interaction overview views (#521). The state machine and interaction overview connect refuse a line that validate() calls an error (into an initial node, out of a final state, onto a region; #538), and the use case connect refuses an include, extend or generalization from an actor and an association between two use cases (#543); a new state machine or overview line's id is transition1 or <from>-<to>, where the canvas used to pick it (#538); a new unguarded line out of an interaction overview decision that has one exit without else gets the guard else (#538). Timing F2 is linear in its spaces, and a change's or message's text over 4,096 characters is refused (#543). A removed message in another letter case is not numbered (#543).
  • ER. A comment link between two tables is refused (#521). On the diff page an IDEF1X entity is marked when a relationship it reads changes how it draws, and only then (#520, ...
Read more

v0.43.0: fixes from audits 17 to 45

Choose a tag to compare

@github-actions github-actions released this 19 Nov 05:32
c04bd48

Install: npm install umlimator@0.43.0, or "umlimator": "github:zintaen/umlimator#v0.43.0".

Audits 17 to 45 confirmed 837 findings: 11 high, 254 medium and 572 low (audit 31 also re-checked an unused run of audit 30, so a few of its findings repeat earlier ones under new titles). All but one are fixed in this release, in 125 pull requests (#392 to #516): 121 fix lanes, one per area and round, plus #392 (the C4 stress ceiling), #403 (dfd-balance made a warning), #427 (the sharded CI) and #446 (the communication timed test's best of five). Each code fix has a test that fails without it, and the release-note findings (about twenty, mostly the 0.42.0 MCP still claim and the import table) are fixed by this section. Audit 38 finding 3 is partly fixed: one of its four state machines (a line through a card, laid out down) is still open (Known gaps). Pictures change only where the notes below name them; bench/expected.json changes for two unfolded map views (#503). The changes a host sees without editing anything: the diff page, its stills and the diff Action mark changes on typed views (#508, #516); diff() also says changes to stories, lenses, the map title and other top-level fields (#460) and says a card reorder that moves the picture (#502); validate() reports more on hand-written models (a line id that is also a card id, a label or title that is not text, a story step on a line the view does not draw) and reports dfd-balance as a warning (#403); a map line weight given as a string draws at weight 1 (#452); apply() refuses a few edits it used to take (hiding a view's subject or an element that holds it, an add or reparent under a node only one view holds); and render leaves out intake logos outside the model's folder, avatars that are not data URIs, example images given as addresses and a model's own icons table. What changes for callers:

  • Core and layout. Every type draws, edits and validates a view's own nodes (view.nodes): the core wraps each type's hooks once (withOwnNodes, src/core/registry.js), where several types used to drop them (#425; audits 23 and 24). Deleting a view-own partition, state or owner no longer deletes the model nodes inside it (audit 23 finding 0 and audit 25 finding 7, both high; #425, #432). apply() refuses hide of a view's subject or of an element that holds the subject as a member, with hide: "X" is the subject of view "V": change the view's subject, or delete it from the model (no command deletes a view) (#393), refuses an add or reparent under a node that one view alone holds (#428), and keeps a function in a command value by reference instead of throwing (#440). hide works out the whole set of ids before it filters a view's own lines, so the result no longer depends on list order (#483). layout() no longer throws on a sequence view whose id is a lifeline's id (audit 24 finding 0, high; #428). A name the author broke into lines is drawn one line per line, and its box grows to hold it (#423, #429). In a pinned map view a box no longer grows over a card it does not hold (audit 41 finding 0, high; #499), and check() has a new issue for that case, family "X" lies over "Y", which it does not hold; an unpinned card in a pinned view takes a clean slot near its box whose lines run forward (#503, #505). Text that exactly fits its room is no longer cut with an ellipsis (#467), a long card text no longer freezes render() (#436), and very deep member nesting no longer overflows the stack (#478). Undo and redo of a card drag on a typed view restore the picture (audit 33 finding 0, high; #468). A process view (mainSteps or render: 'process') with no boxes has a 38 px default column gap, as lib/umlimator.d.ts now says (#483, #487). A map line whose weight is a string such as "2" now draws at weight 1, as the "drawn as 1" warning of validate() always said (#452). In lib/umlimator.d.ts a Geometry edge's weight, wk and lbl are optional, since typed views leave them out (#452). Internally (src/core/registry.js; not public API: lib/umlimator.d.ts declares none of them and no export registers a type), the type registry has four new optional hooks: drawn(model, view) gives the model line ids a view draws (DFD and the C4 views; #487), touches(model, view) the ids outside the view whose change changes its picture (profile and ER; #495), drawnKeys(model, view) keys for the lines a view draws, implied ones included (C4 static and deployment; #497), and edits.field(model, view, id, path, value) lets a type refuse a properties-panel field edit (#484); withOwnNodes also wraps drawn and drawnKeys (#502). check() says "runs back inside its own box" for typed views (#444), "not drawn" for a BPMN line it keeps but does not draw (#443), and label "L" has no room on edge E: only its step N shows for a C4 dynamic step label cut to its number (#426).
  • diff(), the diff page and stills. The diff page, its stills and the diff Action draw change marks on typed views (audit 44 finding 18, high; #508): a NEW, CHANGED or PLANNED tab, a removed shape faded, dashed and struck through, and the change word in its accessible name and keyboard key. #516 extends this to a sequence or timing view's own messages and fragments (audit 45 finding 10, high), typed boxes and family frames (packages, nodes, composite states, C4 boundaries, cloud groups), C4 implied lines, and a map line's key and title. diff() reports stories, lenses (by id), the map title and any other top-level field ("changes the model (root, meta)"; #460). A map card reorder is said when it moves the picture: "moves X after Y", "moves X to the start", or "reorders N cards" when more than three moved (#502); a view whose order changes nothing drawn reads nothing (#505), and a fully pinned view with lines is laid out in both orders to judge it (#508). The summary says "to and from X" for a card at both ends of a change (#440). diff().views lists a typed view whose picture changes through an element it does not list (profile stereotypes, IDEF1X relationships, C4 implied lines, icons) and leaves out one that does not draw the change (#495, #497, #502, #505). The step-order check no longer builds a quadratic table (audit 21 finding 0; #416), and diff() no longer throws on a cycle, a BigInt or a host function in a model (#440, #445). diff --base and the diff Action: a moved or renamed model reads as moved (#430), a model in a dot folder keeps its stills (page stems start with %2E, and action.yml uploads hidden files; #435), a non-JSON file is not reported as a broken model (#479), a model whose disk spelling differs in case reads as modified (#497, #502), the diff sketch keeps self-loops (#476), and a file that nests too deep says "nests too deep to read" instead of a traceback (#413). Correction to the 0.42.0 note (audit 17 finding 22, audit 20 finding 29): the CLI diff and the diff Action take a still of a newly added view; the MCP diff tool takes no stills and lists the view in views.
  • validate() and rules. validate() errors when a line id is also a card id and warns on a label that is not text (#452); it leaves out a Symbol or a value whose toString or toJSON throws, as "a value no text is read from" (#460); it warns on map, story, lens, rule and lane titles that are not text (#473), and on any panel text field a typed view lists that is not text, with "not drawn" for fields the picture never draws (#507, #512). A story step that names a line the view does not draw is an error ("the view does not draw it"; #487); a communication view's message rows are selectable by steps again (#495). A line id written a->b with no #n that names no line gets "names no line" (#499). A change mark that is not one the renderer draws is warned (#516). dfd-balance is a warning, not an error (the maintainer's decision of 16 Nov 2026; #403), so an unbalanced DFD level no longer fails validate(). New rules: generalization-cycle on the use case view, an error that shares the class view's wording so validate() says it once when both views exist (#453), timing-kinds (#459), and multiplicity on the component and object views (#515). Rule messages name kinds in lower case with an article ("a class") (#459). The state machine, use case, activity, BPMN, cloud and SysML rules now judge a view's own lines (rounds 20 to 23; #409, #415, #417, #421, #426), and an element of no type is judged as the kind the view draws it as (#447, #456). The flowchart and BPMN rules run in near-linear time: 2,000 connectors took 17 s and now take 20 ms (#472, #474).
  • Page, keyboard and accessibility. The standalone page's Export > Map model (JSON) writes the model as given: no internal _id, parents kept (#452, #461). Export file names keep letters in any script: a CJK or Vietnamese title no longer gives -.json (#464). map.update() no longer drops a new model when both models hold a value that throws when read (#462), and the page draws a model whose stories is not a list (#420). The page pill, the About box, the views list and the search palette count drawn elements, not nodeIds (#483, #487). L on a line whose far end is a box is refused with "Pick a card to start the line from" (#483). An element labelled "" is named by its id in every typed view, as on maps (#473, #477), and an untyped card is read with the kind the view draws it as (#444, #456).
  • UML structural. An association's or link's end labels keep clear of line labels, cards and box headers (#486): in sales-classes domain and its copy in bookshop-atlas, the end label "orders" moves up 4 px. Member names that clash are refused where the rule would flag them: class, object, profile, component and composite member rows, the component palette's Port and F2, and the composite Name field (#496, #498, #501, #507). A comment link drawn towards a comment is...
Read more

v0.42.0: fixes from the sixteenth audit

Choose a tag to compare

@github-actions github-actions released this 16 Nov 05:21
7ca8f83

Install: npm install umlimator@0.42.0, or "umlimator": "github:zintaen/umlimator#v0.42.0".

The sixteenth audit confirmed 29 findings. All are fixed in this release, in five pull requests (#386 to #390), each
with a test but one docs-only fix (finding 3: the code was already right); findings 1 and 21 are one defect, so there
are 28 fixes. Two change results a host can see without editing anything: rules() no longer judges a typed view's
hand-written containers, and diff() lists a newly added view.
Pictures change only where something was not drawn
(member, flow and node stereotypes, an anonymous part's name, a lifeline's second head); bench/expected.json is
unchanged. What changes for callers:

  • Rules, lenses and diff(), round 16 (#388). rules() ignores a typed view's hand-written containers, as the
    PDF's tables already did: a type that lays its view out never draws them (validate() warns own-boxes), so a rule's
    { container } end and its box scope find no box there, and a box cycle through them is no longer reported. Lenses,
    check()'s rule lines and the PDF's Rules section ("Applies in") read the view the same way. This changes rule
    results for a typed view with hand-written containers
    ; maps and typed views without them judge as before. diff()
    puts a newly added view in views
    and marks its own cards and lines added, as a removed view's are marked removed;
    its cards are in the summary ("adds X"), its lines are styled added but not listed one by one. The CLI diff, the
    diff Action and the MCP diff tool now take a still of the new view. diff(null, model) marks every view's own lines
    added too. present is compared per card, with the card ("changes A (present) in the view V"), no longer as a
    view field: a hide now says only "takes A out of the view V". The PDF cover counts a view's own line apart from a
    model line with the same ends (both were named a->b#0). The docs now say repair (the option and the view field)
    applies to map views; a typed view's lines are never port-repaired, as the code already did.
  • Page, round 16 (#388). The details panel's title is an <h2> and its sections <h3> (they were <h3> and
    <h4>, a skip under 0.41.0's new <h1>); the views list's heading, Find's "Nothing called…" and an empty view's
    "Nothing here yet" are <h2> (were <h4>). They are styled by selector, so the page looks the same.
  • UML, round 16 (#390). A member's stereotypes are part of its row's text: a class or SysML block member row
    draws them before the row («column» on the atlas's Order.placedAt now shows), printMember writes them for the PDF
    and the panel and parseMember reads them back. Typing a row with no «…» clears the member's stereotypes; a SysML
    block row reads them after the keyword (part «x» foo: T). The profile view prints members without their
    stereotypes
    , beside the applied ones, so nothing shows twice. Composite structure: a part or role with no name is
    named as drawn, : Engine [1]
    , by its ports, connectors, role bindings, describe(), the PDF and remove; an
    unnamed collaboration use draws : Collab with no leading space; F2 on a collaboration use reads name : Collaboration (it returned null; the drawn text no longer becomes its label), and F2 on the subject's own port
    reads name : Type
    (a name alone keeps the type). Component ports read name : Type too, through a new
    edits.rename hook. Use case: F2 on an extend changes nothing when the text is unchanged, finds the condition by
    matching brackets from the end ([cart.items[0] is …]), and is refused with an error pointing to the properties
    panel when the drawn text does not read back
    (a name ending in [..]). Activity and interaction overview: F2 on a
    flow whose name does not read back is refused (as a state transition's is); flows draw «a» before name [guard]
    and say it, F2 strips it; partitions, decision and merge nodes, interaction uses and inline interactions draw their
    stereotypes in their name; initial, activity final, flow final, fork and join nodes no longer offer Stereotypes in
    the panel. Sequence: a lifeline created again in another alt operand draws a second head at that create, and the
    create ends on it
    ; the layout gives that row a head's room and heads[i].again lists each extra head's top y (only
    when there is one, so other geometry is unchanged).
  • Other types, round 16 (#387). C4: each line the type implies is a row of the PDF's Lines table as drawn
    ("Shopper → Shop | Browses [+1] | Implied relationship"), one per drawn line, and the page header and cover count it
    (they said 0 lines). A deployment view's inline relationship ending on a node drawn as a box gets the c4-box-line
    warning (path views[i].edges[k]); a container or component view listing a null id with a line between null ends no
    longer overflows the stack in layout(), check() and the PDF. ER: x int FK NOT NULL is read (NOT was taken as
    the FK's target). Flowchart: a flow written inline in the view refuses a drag or Alt+arrows ("A flow follows its
    nodes: move a node instead"). BPMN: the first lane added to a pool that holds flow nodes takes them in, boundary
    events with them; data and annotations stay in the pool.
  • Readers and CLI, round 16 (#389). Python flowchart import: an outer subgraph with no end draws its inner boxes
    at the top level (render refused the model); a subgraph id opened again adds to the first box, and a box inside
    itself, directly or through a cycle, is drawn at the top level with "subgraph P is inside itself: drawn at the top
    level". The Mermaid class reader closes a class body at its first } and reads the rest of the line again, so
    namespace X { class Y { ... } } closes X; a } that closes nothing is reported. A model whose stories, or a
    story's steps, is not a list is refused
    by render, diff and the MCP server with "stories is not a list",
    "stories[i] is not an object" or "stories[i].steps is not a list" (render accepted it, and MCP list_views and
    play_story ended in an internal error). timelapse fills its template in one pass, so model text holding a
    placeholder stays data.
  • Documentation site, round 16 (#386). Inline code reads at WCAG AA on a table row's tint in both themes
    (--vp-code-color #0550ae light, #6cb6ff dark; links keep the accent). Every page in examples/ has an <h1> (ask,
    drift, live, playground and replay make the header title one; embed and timelapse have a visually hidden one). The
    standalone page guide says what a link keeps: a view, a selected card, a story step or a lens, not a selected line or
    box.
  • Known gaps. Still open from 0.41.0 (checked on main with a small script: the JavaScript Mermaid readers still
    decode #55296; to a lone surrogate, a typed view still gets no "listed twice" warning for view.edges, 21 of the 30
    typed examples still do not set "$schema", a composite or SysML internal block view's PDF Lines rows still name a
    part by its id): a box has no Tab stop; the keyboard reaches it through the outline. A double-click (or Enter) on a
    box does not open its view (the 0.24.0 gap). Deep nesting is super-linear outside the core. The requirement layout
    leaves out a link into a box nested more than 64 deep from its ranking. Typed hooks that answer Alt+arrows themselves
    were not checked on views laid out down. reach() from a model id that the view draws under another id returns only
    that element. A negative step duration plays 500 ms while validate()'s warning says 4000 ms. Mermaid C4 macro
    arguments keep entity codes as written. describe() of an inline interaction does not say it opens a view. Room for a
    label in a turned view is still mostly along the line. The map flowchart and Structurizr DSL readers turn a U+2028
    inside a label into a space. The unfolded call behaviour box is a plain container frame. A page rendered before 0.33.0
    with a numeric view id, before 0.36.0 with a numeric card id, or before 0.37.0 with a view with no id, still ends in a
    traceback in stills. Three or more delegations from one port into a grid of parts may still cross. Other files in
    src/bpmn may still key plain objects by id. The typed Mermaid reader's quote join skips %% comment lines but not the
    body of a multi-line %%{ }%% directive. The PDF tables read an open package's qualified name off its drawn title. No
    example reaches the C4 views lift branch or src/sysml/sysml.js's frame branch; only select() has a browser test of
    its own among Find and the panel links. The double-click tests send synthetic events. The SysML block definition view
    has no own list of line kinds. The SysML tables RQ_REL and BD_ORDER are still plain objects. An MCP page tool on a
    model that has never rendered still says it cannot read the model. validate() still accepts a positional name
    (docs/diagrams/risks.md F9). diff() numbers id-less lines among id-less lines only, where Ref names count every line
    with the same ends. The profile, package and SysML block definition conformance notes point to the class or package
    note for the shared rules. No typed card draws a new, changed or removed badge, so a restored part, port, fragment or
    region draws as present (only its lines show the removal); if a restored owner's members moved elsewhere in after,
    they could come back twice. Component validate() messages still name ends by the bare label. A C4 deployment
    instance's Name field still writes its label, which shows nowhere. #362's tests were not run against the unfixed code.
    A removed operand under a fragment is still summarised through the type's order, and a member of a node that lives
    only in one view is not restored. The details panel cuts a part's label at " : " ("checkout"). The panel lays ...
Read more

v0.41.0: fixes from the fifteenth audit

Choose a tag to compare

@github-actions github-actions released this 16 Nov 02:13
4481538

Install: npm install umlimator@0.41.0, or "umlimator": "github:zintaen/umlimator#v0.41.0".

The fifteenth audit, the first to cover the documentation site, confirmed 40 findings. All are fixed in this release, in
five pull requests (#380 to #384), each with a test; findings 5 and 27, 18, 26 and 31, 30 and 35, and 32 and 36 are one
defect each, so there are 35 fixes. #384 fixes a regression of 0.40.0's request/reply port swap (#377): it ran on
maps with repair: false, which turned their port repair off, and it could leave some C4 views with more crossings. Maps
draw as in 0.39.0 again; bench/expected.json and every pinned example's crossing count are unchanged. What changes for
callers:

  • Layout, round 15 (#384). The request/reply swap runs on typed views only: a map's repair: false means no
    repair again, as docs/guide/model.md says, so a map that set it draws as in 0.39.0. A typed view of up to 30 cards
    that kept a swap is judged on the finished picture
    : it is laid out once more without the swap, after the type's own
    finishing steps (BPMN's, for one), and that picture is kept when routeAudit finds fewer issues. A pinned C4 container
    view (five containers, three call/reply pairs) is back to 9 issues (0.40.0 drew 13); of 240 random C4 container views,
    none is worse than before #377 and 78 are better. A view of more than 30 cards keeps the swap as the pass judged
    it
    , so the C4 stress view takes no extra layout and a large C4 view can still come out worse than without the swap.
  • diff() and the PDF, round 15 (#384). diff() reports a change that moves nothing but the layout and lists the
    view: a kept card's pin ("moves Payment provider in the view What runs"), any other view field ("changes the view V
    (caption, lanes)"; every key but id, title, nodeIds, nodes, edges, containers, nodeOverrides, layout
    and fragments, so render, direction and repair too), a box's tone or badges ("changes the box B (tone) in the
    view V") and added, removed or changed rules ("adds the rule T", touching the views where rules() finds something
    different). The bike-share diff fixture moves Payment provider's pin, so its summary now says so. The PDF cover's line
    count matches the Lines tables
    : it counts the union of the line ids each view's table lists (tablesOf()'s new
    lineIds), so a typed view's self-lines count (checkout-sequence 10 lines, was 9; order-service-structure 8, was 0).
  • Page and API surface, round 15 (#380). A card with no label is named by its id in its tooltip (<title>) and
    in the tooltips of its lines (alpha → Charlie), as its accessible name already was, and on the standalone page in
    Find's result and in "Did you mean". <umlimator-map> with no theme follows VitePress's light/dark switch:
    inside VitePress's default theme (.VPContent), a map is light whenever <html> is not .dark, whatever the system
    prefers (the rule is in :where(), so a host's own --um-* still win); elsewhere the system setting decides, as
    before. The standalone page's title is its <h1> (h1.mbrand, the bar looks the same). setView() is declared
    Promise<boolean>
    in lib/umlimator.d.ts, what it has resolved since 0.14.0, so if (await map.setView(...))
    compiles under tsc --strict; code that awaited the old type still compiles. The Element doc comment names the four
    sysml.* types. otlpSpans() skips attributes that are not a list (the span reads service: null, and trace no
    longer ends in a Node stack trace) and reads a name that is not text as null.
  • UML, round 15 (#382). F2 stores only the label: on a communication message row it strips the drawn number and
    «create»/«destroy»; on a use case include or extend it strips the keyword and stereotypes, reads a trailing
    [condition] back into props.condition and refuses a changed (points) with { error }; on a line a class,
    package, profile, component, deployment or object view owns in its own edges, it strips the keyword too.
    uml.communication and uml.use-case gain an edits.rename hook. The component view draws only a uml.Component
    (or an element with no type) as a component
    ; another kind is a classifier with its keyword («node», «actor»), and
    the deployment view gives an interface or actor its keyword. Composite structure and component views draw the
    stereotypes the panel offers: on a connector (before its label, and said), a part (over its name; the box grows 14 px
    for each after the first), a port and a ball; component and deployment ports, interfaces and artifacts say them
    ("(a, b)"). A part or collaboration use with no name and no type is drawn and said by its id. State machine: a drag
    that moves a direct substate of an imported region-mixed state into one of its regions is allowed (only a move that
    gives a state a direct vertex is refused). The timing note says where a duration between two lanes sits.
  • Other types, round 15 (#381). C4: F2 on a relationship written inline in a view no longer adds its technology to
    the label a second time.
    ER: a row's NOT NULL leaves the column not nullable (it made it nullable and put NOT
    in its type); NOT NULL with NULL is refused ("NULL is written twice"); the PDF text names an inline relationship.
    Flowchart: the PDF text and the connect hook count inline flows (an inline decision exit is yes, the new one no). SysML:
    F2 on a requirement relationship or a block definition line stores only the label (block definition gains an
    edits.rename hook), and F2 on an internal block connector with an item flow sets props.itemFlow.item, the text
    drawn (empty text is refused). The row port : Integer is a value property named port in parametric, composite
    structure and internal block views (a port row needs a name after the keyword); a parametric param : Real with no
    name is refused. Mindmap: Show on a lone hidden topic runs the type's Show ("Showed X"). BPMN: a flow node added with a
    pool that has lanes goes into the pool's first lane that holds no other lane.
  • Readers, MCP and documentation site, round 15 (#383). The Mermaid class reader closes a block at any }, as
    Mermaid's lexer does: +quack() }, class Cage } and namespace Zoo { class Cage } no longer swallow the rest of the
    file. MCP: a null (or anything not a string) in a view's nodeIds or stepIds is a tool error saying where
    ("views[0].nodeIds[1] is not a string"; it was "Internal error"), and show_view, highlight and tour with view
    "" answer "no view ''" (it cleared the tour and story). Site: a same-page link written with GitHub's heading slug now
    reaches its heading on every page (the changelog's links were dead); the import and export guide says export writes
    BPMN XML only and the seven Mermaid writers are internal to the module; docs/api/typed-diagrams.md states each type's
    default direction as the schema does (down for a flowchart, profile, SysML block definition or requirement view, a
    sequence view always); docs/conformance/gcp.md and examples/README.md say what the site and a copy draw for cloud icons.
  • Corrections to earlier sections. 0.14.0 says of setView(): "The declared type stays Promise<void> | void".
    From 0.41.0 it is declared Promise<boolean> (#380). 0.26.0's known gaps say Cloud-DNS, Cloud-Load-Balancing,
    Cloud-CDN and Pub-Sub draw a glyph; since 0.40.0 (#378) they draw their category's icon.
  • Known gaps. Still open from 0.40.0 (checked on main with a small script: the JavaScript Mermaid readers still
    decode #55296; to a lone surrogate, a typed view still gets no "listed twice" warning for view.edges, 21 of the 30
    typed examples still do not set "$schema"): a box has no Tab stop; the keyboard reaches it through the outline. A
    double-click (or Enter) on a box does not open its view (the 0.24.0 gap). Deep nesting is super-linear outside the
    core. A composite structure or SysML internal block view's PDF Lines rows name a part by its id, not its drawn name.
    The requirement layout leaves out a link into a box nested more than 64 deep from its ranking. Typed hooks that answer
    Alt+arrows themselves were not checked on views laid out down. reach() from a model id that the view draws under
    another id returns only that element. A negative step duration plays 500 ms while validate()'s warning says 4000 ms.
    Mermaid C4 macro arguments keep entity codes as written. describe() of an inline interaction does not say it opens a
    view. Room for a label in a turned view is still mostly along the line. The map flowchart and Structurizr DSL readers
    turn a U+2028 inside a label into a space. The unfolded call behaviour box is a plain container frame. A page rendered
    before 0.33.0 with a numeric view id, before 0.36.0 with a numeric card id, or before 0.37.0 with a view with no id,
    still ends in a traceback in stills. Three or more delegations from one port into a grid of parts may still cross.
    Other files in src/bpmn may still key plain objects by id. The typed Mermaid reader's quote join skips %% comment
    lines but not the body of a multi-line %%{ }%% directive. The PDF tables read an open package's qualified name off
    its drawn title. No example reaches the C4 views lift branch or src/sysml/sysml.js's frame branch; only select() has
    a browser test of its own among Find and the panel links. The double-click tests send synthetic events. The SysML block
    definition view has no own list of line kinds. The SysML tables RQ_REL and BD_ORDER are still plain objects. When
    two operands of one alt each create a lifeline, the second create arrow lands on the stem below the single head.
    printDoc's rules section and rules() still count a typed view's hand-written containers as boxes a rule can name.
    An MCP page tool on a ...
Read more

v0.40.0: fixes from the thirteenth and fourteenth audits; documentation site

Choose a tag to compare

@github-actions github-actions released this 15 Nov 23:30
4b4d306

Install: npm install umlimator@0.40.0, or "umlimator": "github:zintaen/umlimator#v0.40.0".

The thirteenth audit confirmed 22 findings and the fourteenth 24. All 46 are fixed in this release, in nine pull requests
(#365 to #369 for round 13, #374 to #377 for round 14), each with a test; in round 13, two findings (an --out named in
other case, and one named by a hard link) are one defect with one fix. Maps draw as before and bench/expected.json is
unchanged. Typed views change in one way: #377 removes crossings where a request/reply pair between two cards crossed
itself (listed below). The release also brings the documentation site at zintaen.github.io/umlimator/ (#370 to #373)
and category icons for Google Cloud products the pinned pack has no icon of (#378). What changes for callers:

  • Core, round 13 (#369). Story line names (a->b#n) are counted per list: the model's list, and each view's own
    edges list. lineNames() now returns a Map from list to names (-1 for the model's list, i for view i's own
    list), each a Map from a name to its lines; 0.39.0's Map from name to lines is one entry of it. A delete or a hide
    renames or clears a name only in the list it touched and only where that list is drawn (steps, pins, present and
    overrides on a view that draws it); before, a step on one view could move onto a line of another view between the same
    cards. validate() checks a step's a->b#n against the list its view draws. diff() says a member gone from an
    element that stayed as "removes battery from EBike"
    (it said "changes EBike (members)") and no longer repeats its
    connectors; a deleted part or port that a removed line ends on comes back change: 'removed' at its old index, so its
    connectors draw rose and dashed and the diff model validates (a deleted class attribute or internal transition is said
    but not put back). A view that dropped its edges list gets a list built from the lines it draws, so its own lines
    come back marked removed and removed lines to removed cards stay drawn, whether or not it put a line in. render() no
    longer throws on change: 'constructor' or '__proto__' (no badge is drawn). The details panel names a port or
    parameter end as drawn ("requests of checkout", "capacity of usable"), a port's own lines are found, and a row whose
    end is drawn only in another typed view opens that view with the end selected; when no view draws an end, the status
    line says so. A selected part's rows now name the far port ("quotes of pricing"), not the far part.
  • UML, C4 and mindmap, round 13 (#367). The PDF Lines table lists self-lines on typed views (class, object,
    package, component, a state machine's self-transitions); map views still leave them out. State machine: dropping an
    initial or history pseudostate into a one-region state goes through the same guard as other moves, so a second one is
    refused with { error }, and the Owner field no longer offers an owner that already holds one. Timing: F2 or N splits a
    name only at a lone colon, so Shop::Worker stays one name (http://api still splits). C4 deployment: T on an
    instance always sets its label to the new container's name
    (before, a label of its own was kept). Information flow:
    naming a flow whose text equals the drawn list sets only the label. Mindmap: N, Delete, Shift + Delete and the
    outline's Show leave the other first-level branches on the sides drawn
    ; Delete and Show run one layout, so "Delete
    half" of the 20,000-topic chain takes about 160 ms (linear).
  • ER, flowchart, DFD, information flow and Mermaid readers, round 13 (#368). Lines written inline in a view's
    edges are now checked by validate()
    as model lines are (ER relationship ends, information flow conveyed and ends,
    every DFD flow rule, flowchart flow ends); a new typedLines() in src/typed/layout.js lists them with their paths. A
    DFD process fed only by inline flows no longer gets dfd-process-io.
    The Mermaid state reader reads Moving:::cls as
    a state with its class reported skipped (it made a note "::cls"), and Crash:::cls : it broke gives Crash that
    description. The Mermaid ER writer writes %% references: only to a column it writes, and names the others under %% not written:; the reader drops a %% references: naming no column it read and reports it skipped. The README's
    4a model table names AWS; the gallery's C4 card says five views.
  • CLI and MCP, round 13 (#365, #366). The --out guard compares files, not only paths: an --out that exists and
    is the same file as an input (a name in other case on a case-insensitive disk, or a hard link) is refused.
    timelapse walks the first-parent line (git log --first-parent -m): a merge is one step and its last frame is
    HEAD's model; a side branch's own commits no longer show up. MCP highlight refuses a Ref whose view names no view
    with show_view's message ("no view 'nope'; the views: ..."); before, the page threw and a later clear failed. check --ignore labelNoRoom also drops "step N has no room on edge". The README file map lists pack, export and
    umlimator_packs.py.
  • Core and CLI, round 14 (#376). A raw hide of a lifeline also drops it from that view's interaction uses'
    props.covers
    , so the model still validates (other props naming model elements are kept; the canvas already did
    this). diff() says a new id-less line once in a view that dropped its edges list ("adds D, from C", not "from C and
    C"). validate() warns of a card source that is not text: nodes[i].source: source is a path or a list of paths: what is not text is ignored. A map card with no label is named by its id in its accessible name and its lines'
    ("Line from a to C"), as nameOf() and the live region already did; no geometry changes. The CLI's --out guard also
    covers trace's TRACE and drift's --match (trace's --out may still be MODEL.json). diff, drift, trace,
    export and the MCP diff tool refuse a JSON object with no views in one line ("FILE: no views: not a map model").
    diff --base --out FILE on an existing file says "diff --base: --out X is a file: name a folder for the pages and
    summary.md" in one line. otlpSpans() skips what is not a list or an object, so trace on malformed OTLP ends in its
    usual one line.
  • UML lines and objects, round 14 (#374). F2 on a line in class, package, profile, component and deployment views
    edits its label alone
    : the drawn keyword and «stereotypes» are taken off (before, «trace» was stored in the label and
    drawn twice); these types gain an edits.rename hook. A line of a kind the view does not draw is a plain solid arrow
    named "Line"
    in component and object views (it was a «dependency», or an undirected Link). The object view draws
    only a uml.InstanceSpecification (or an element with no uml. type) as an instance
    ; another uml.* element is a
    classifier with its kind word ("Component Shop API"). F2 on an anonymous instance opens its name alone, not ":
    Customer". The sequence and communication conformance notes say self-lines are in the PDF Lines table.
  • C4, ER, information flow, mindmap, Mermaid writers and docs, round 14 (#375). apply() carries a renamed label to
    the elements that name it
    : when set label renames an element, each element whose type marks the prop pointing to it
    named and had the same label gets the new one. A registry refs value may now hold several words ('cascade named'; delete cascades still match cascade); C4 deployment's props.container is 'cascade named'. So renaming a
    C4 container by the Name field or by F2 on any view renames its instances
    ; an instance with a label of its own keeps
    it, and F2 on a container is the canvas's default again (its hook returns null). ER: an identifying relationship written
    inline in a view makes the child dependent. Information flow: inline flows count in "conveyed by", rows, text, rename
    and remove; a view with no list draws only the model's flows. Mindmap: the outline's Show sets no side on topics it
    puts below the first level. The Mermaid class, sequence and state writers name what they drop (%% not written: ID: ext, property P). The Google Cloud and Azure notes drop the icons-only update() limit lifted in 0.28.0; AWS is
    in docs/editing.md, examples/README.md and the schema's iconPacks description.
  • Layout, state machine, communication and parametric, round 14 (#377). Laid out right with repair: false, two
    lines between the same two cards that cross swap ports
    (both ends, then one), kept only when the issues drop; lines
    ending on a port are left alone. Pictures that change, crossings only: examples/bookshop-data-flow.json level 1, 2 to
    1, and the take-payment level 2, 1 to 0; examples/bookshop-order-to-shipment.json, 5 to 4; stress fixtures: ER all 18
    to 17, information flow edge-cases 2 to 1, C4 all 136 to 133, use case all loses its "share a line" pair, composite all
    21 to 19 (5 to 4 down). The swap tries cost the C4 stress fixture's full layout about 15% (512 to 591 ms in CI). State
    machine: a drop on an orthogonal state's own box, N on it, and the Owner field are refused with "...: put it in one
    of its regions" (stGuard refuses a new region-mixed warning too); an imported region-mixed state draws its direct
    substate beside its regions. Adding a Region to a state with direct substates moves them into a first, unnamed
    region
    and adds the new one beside it. Communication: check() reports a connector routed through another
    connector's message rows, and the router's warning names the stack ("the messages on b–a"); the route is unchanged.
    Parametric: port, proxy port and full port member rows are refused on a parametric view.
  • Documentation site (#370 to #373). Th...
Read more

v0.39.0: fixes from the twelfth audit

Choose a tag to compare

@github-actions github-actions released this 15 Nov 17:33
78a613d

Install: npm install umlimator@0.39.0, or "umlimator": "github:zintaen/umlimator#v0.39.0".

The twelfth audit confirmed 28 findings. All 28 are fixed in this release, in five pull requests (#359 to #363), each
with a test; two of the findings (a delete and a hide leaving a story step on the wrong line) are one defect with one
fix. No map or example draws differently and bench/expected.json is unchanged; the details panel of a part or a port
reads differently, and a requirement view with an unknown direction is now laid out right. What changes for callers:

  • Core (#360). Delete and hide now keep a story's positional line names (x->y#n) on the lines they named. When a
    delete or a hide removes one of several id-less lines with the same ends and a line left only moves place, the name is
    renamed ('a->b#1' becomes 'a->b#0') in story steps, lenses and rules, in strings and in Refs (id, node,
    ids), and names used as object keys are renamed all at once, so two names that swap stay right; a name is cleared
    only when its line went. Before, deleting a line with an id cleared the name of a surviving id-less line with the same
    ends, or left a step quietly pointing at the next line, and hide left a step naming a view's own id-less line it had
    removed. lineNames() now returns a Map from each positional name to the lines it names (it was a Set); .has()
    reads it as before. rules() leaves out a self-loop (from === to), which a view does not draw, as describe()
    and the PDF already did; it reported a break on one. diff(): a view that dropped its edges list now gets an
    explicit list
    of the lines it draws, with the lines it puts in marked added (it said "puts the line ..." but marked
    nothing); the drawn set does not change. diff() brings back a removed message's fragment or a removed state's
    region
    : when a removed item's owner (a fragment operand, or a member such as a region) is missing from after, that
    owner comes back from before, marked change: 'removed', at its old index, so the result validates and the state is
    drawn inside its state's box.
  • UML types (#361). Sequence and communication: a self create or a self delete message is now an error of
    validate(), a create-once or delete-once error, as the connect hook already refused it; the two rule texts now
    end "never by itself" ("a lifeline is created at most once, by the first message to or from it, never by itself").
    Component: line accessible names, describe() and the PDF rows name each end as the picture does (Web to orders::Api, and <port> of <owner> for a port), not by the bare label. Composite structure: in a view with no
    edges list, connector-part no longer warns about a connector that belongs to another classifier's own structure (a
    regression from 0.38.0); a collaboration with no label is found by its id, so the false collaboration-named warning
    goes and binding-role and the role picker work again; describe() no longer throws on a part id holding ->
    (validate() still reports the id). Timing: a reply with no replyTo gets "names no call in replyTo: a reply from
    payments to worker needs a call from worker to payments sent no later" (it read "m1 answers undefined"), and both
    reply-call messages name lifelines by name. Information flow: F2 then Enter on a flow's text as drawn changes nothing
    (it could swap what the flow conveys when a name held ", ").
  • C4, DFD, ER, BPMN, mindmap and SysML (#362). C4 deployment: an instance is named by its container in line
    names and describe(); T also updates the instance's label when it still equalled the old container's name; F2
    on an instance is refused
    with "An instance is named as its container: T picks another container". DFD: a new
    warning rule, dfd-notation
    (DFD now has seven rules): "dfd-level-1" has notation "gane-and-sarson", drawn as yourdon: write yourdon or gane-sarson (an unknown notation was drawn as Yourdon with no warning). ER: a new
    column's id drops ->
    ("payload->>type" text gets <entity>.payload-type); apply() threw. BPMN: Delete of a
    lane with a node inside it also selected now works
    : the node is moved to the pool, then hidden; Shift + Delete is
    unchanged. Mindmap: Show after Delete puts a first-level topic back on its side (backlog 4a.4); where it goes in
    the order is unchanged and documented (notes/milestone-4a.md §7.3). SysML block definition: member-names now
    judges blocks, interface blocks, constraint blocks and value types
    , operations keyed by their parameter types as for
    a class.
  • CLI and readers (#359). --out naming the command's input is refused before anything runs: "CMD: --out X is
    its input: name another file", for the model, file, page, observed file or either diff file (trace, whose docs allow
    --out MODEL.json, is exempt); before, it replaced the input and exited 0. import of JSON nested too deep reads
    "import: FILE nests too deep to read: nothing written", not a RecursionError traceback. The Structurizr DSL importer
    stops walking views at 500,000 elements and relationships in all (VIEW_WORK, as the JavaScript reader's cap): that
    view and the rest are left out and said once (541 KB of DSL took 111 s and 5 GB). The Mermaid state writer names under
    %% not written a transition whose ends are both left out. map-repo's cli.py clone-failure message asks for a git
    clone of the tag (git clone --branch vX https://github.com/zintaen/umlimator.git DIR/vX). The 0.14.0 note above,
    which says UMLIMATOR_CLI_CACHE names "a folder that holds the release", means a git clone of the release's tag.
  • Page, MCP, schema and docs (#363). The details panel names a part or a port as drawn ("checkout : CheckoutFlow
    [1]", kind word Part or Port), not by its internal id with "Script INTERNAL", and a collaboration use's rows name its
    parts as drawn. The MCP highlight with no view now finds the view of a line that ends on a port, a port on a part's
    type or a box (it landed on the current view and dimmed every card). The JSON schema's typed view.direction text
    reads "default right; down for a flowchart, a profile, a SysML block definition or requirement view". A requirement
    view whose direction is neither right nor down is now laid out right, as validate()'s warning says (it was laid out
    down), and the Mermaid requirement writer writes direction LR for it ("written as Mermaid's LR, as it is drawn"; it
    wrote TB). The gallery's state machine card lists the pseudostates order-states.json draws.
  • Known gaps. Still open from 0.38.0 (checked on main with a small script: the JavaScript Mermaid readers still
    decode #55296; to a lone surrogate, a typed view still gets no "listed twice" warning for view.edges, validate()
    still says nothing of a non-string source entry, 21 of the 30 typed examples still do not set "$schema"): a box
    has no Tab stop; the keyboard reaches it through the outline. A double-click (or Enter) on a box does not open its
    view (the 0.24.0 gap). Deep nesting is super-linear outside the core. A composite structure or SysML internal block
    view's PDF Lines rows name a part by its id, not its drawn name (#363 fixed the details panel only). The requirement
    layout leaves out a link into a box nested more than 64 deep from its ranking. Typed hooks that answer Alt+arrows
    themselves were not checked on views laid out down. reach() from a model id that the view draws under another id
    returns only that element. A negative step duration plays 500 ms while validate()'s warning says 4000 ms. Mermaid C4
    macro arguments keep entity codes as written. describe() of an inline interaction does not say it opens a view. Room
    for a label in a turned view is still mostly along the line. The map flowchart and Structurizr DSL readers turn a
    U+2028 inside a label into a space. The unfolded call behaviour box is a plain container frame. A page rendered before
    0.33.0 with a numeric view id, before 0.36.0 with a numeric card id, or before 0.37.0 with a view with no id, still
    ends in a traceback in stills. Three or more delegations from one port into a grid of parts may still cross; this
    needs a routing change. Other files in src/bpmn may still key plain objects by id. The typed Mermaid reader's quote
    join skips %% comment lines but not the body of a multi-line %%{ }%% directive. The PDF tables read an open
    package's qualified name off its drawn title, and only when the title ends in :: and its label. No example reaches
    the C4 views lift branch or src/sysml/sysml.js's frame branch, so the prototype sweep does not check their byId;
    only select() has a browser test of its own among Find and the panel links. The double-click tests send synthetic
    events. The SysML block definition view has no own list of line kinds, so it draws every kind. The SysML tables
    RQ_REL and BD_ORDER are still plain objects (SYS_IB_PROP, SYS_PAR_PROP and SYS_PAR_SUBJ have no prototype).
    When two operands of one alt each create a lifeline, the second create arrow lands on the stem below the single
    head. printDoc's rules section and rules() still count a typed view's hand-written containers as boxes a rule can
    name. An MCP page tool on a model that has never rendered still says it cannot read the model. validate() still
    accepts a positional name (docs/diagrams/risks.md F9), and warns only when it names no line. diff() numbers id-less
    lines among id-less lines only, where Ref names count every line with the same ends; the keys never leave diff().
    The profile, package and SysML block definition conformance notes point to the class or package note for the shared
    class rules instead of naming each one. The 0.38.0 gap of a partial delete shifting the names of the lines left is
    closed by #360. N...
Read more

v0.38.0: fixes from the eleventh audit

Choose a tag to compare

@github-actions github-actions released this 15 Nov 15:49
27c881a

Install: npm install umlimator@0.38.0, or "umlimator": "github:zintaen/umlimator#v0.38.0".

The eleventh audit confirmed 23 findings. All 23 are fixed in this release, in five pull requests (#353 to #357), each
with a test that fails without its fix, except one that changes only a comment (the requirement reader's header). No map
or example draws differently and bench/expected.json is unchanged; only the keyboard focus ring looks different. What
changes for callers:

  • Core (#357). diff() now says when a view hides or shows a model line that has no id ("takes the line from A to B
    (pays) out of the view v", "puts ..."), lists that view, and returns the line in the view's edges marked removed;
    before, it keyed lines by id only and said nothing. A map line from a box to a card or box inside it (at any depth)
    was never drawn; it is now also left out of describe(), rules(), paths(), lenses, the PDF tables and layout
    planning, so they agree with the picture, and validate() warns about it: joins the box "payments" and "db", which it holds: not drawn in view "main" (path edges[i]; for a view's own list, path views[i].edges[j] and no
    view name). layout() still sends the same console.warn (#28), now from context.js; check() stays geometry only;
    typed views are not affected. Delete now clears a positional line name (x->y#n) that no longer exists from story
    steps, lenses and rules, as it clears an id, and validate() warns when a step's select or highlight names
    x->y#n and no line has that name
    ("names no line: the step shows nothing for it"). It is a warning, so a model
    that validated still validates; -> names without #n (a typed view's geometry ids such as owner->child) are
    accepted as before. The keyboard focus ring on lines and typed elements (.line-key:focus-visible .key-ring) goes
    from stroke-opacity .55 to .8: 3.59:1 on the light stage, 3.66:1 on a white card and 4.5:1 on the dark stage, at least
    WCAG 1.4.11's 3:1 (it was 2.33:1 and 2.63:1).
  • UML types and mindmap (#354). Composite structure connect() refuses a connector from a part or box to itself:
    two ports of one part, two ports of the subject, or both ends on one box get "A connector joins two parts or ports of
    two elements: no line runs from a part or a box to itself". SysML internal block and parametric views share that hook,
    so they refuse the same. member-names now judges only classifiers (class, interface, enumeration, data type,
    primitive type, stereotype) and instance specifications, and skips members with no name; this holds for the object,
    package and profile types too. It no longer checks a component or any other non-classifier owner, so two
    same-named ports on a component, or two unnamed regions of a state, are no longer reported by it. In a composite view
    with no edges list, connector-part now warns of a connector whose unnamed end's port belongs to a type of a part
    of the subject. Ports on a collaboration's roles stay supported and are now checked: connector-scope places a role
    end in its collaboration, and connector-part (its description now "an end's part is a part of the subject or a role
    of a collaboration shown, and the end is a port of that part's type") accepts a role of a shown open collaboration;
    docs/conformance/uml-composite-structure.md is corrected. Mindmap: Alt + the arrow towards the root puts the topic
    before its old parent's next sibling when nodeIds is not in pre-order (it went after the parent's later siblings).
  • BPMN, flowchart and conformance notes (#353). The BPMN PDF Elements table lists a pool's lanes, in lane order,
    after the pool's documentation, each as "label — documentation" when the lane has documentation (a documented pool
    lost its lanes, and lane documentation was printed nowhere). Delete of a lane with a sequence flow selected now
    deletes: the line is skipped on a view with no edges list, as the canvas's own Delete does, with the hint "Shift +
    Delete deletes the line" (before, apply() refused the hide and nothing was deleted). A boundary event's
    present.<id>.side named for an Object.prototype key is ignored as an unknown value is. The JSON schema's
    view.direction text reads "(default right; down for a flowchart)", as the layout does. The information flow note no
    longer calls information items supported flow ends; the component, deployment and composite structure notes list
    own-boxes.
  • Readers and writers (#356). The Python map importer's Mermaid flowchart reader is linear on a long line of nodes
    with no closer (a 1 MB line read in 26 to 62 s, now about 1 to 2 s). The Mermaid class writer reports, and does not
    write, an empty stereotype, one ending in >, or one with a space at either end; it reports a value, return or
    parameter type with a space at either end (type …, read back trimmed), still written. The class and sequence writers
    skip and report an id with a space or tab at either end (view, class, note, member, relation and link ids; view,
    lifeline, message, use, fragment and operand ids), as the state and flowchart writers do; their report for a view id
    reads "which a hint cannot carry" (was "which has a line break"). writeBpmnXml reports a blank id ("a blank id,
    which a reader reads as none"). The requirement reader's header names the copy-text exception.
  • CLI and MCP (#355). diff (both files), drift, trace, export and the MCP diff tool's other_model_path
    refuse a model render refuses, naming the file at fault; diff --base checks each version under its own name ("its
    version at REF: ...", "it: ..."). The MCP highlight with no view picks a view that has the line for a from->to#n
    name, the card of a chip or badge, and a box Ref's container. diff --base's "No picture" line writes view ids
    through the same flattening as the rest of the summary, so @name, #42 and <!-- mention, link and hide nothing.
    trace --view '' exits with "trace: --view needs a view id" before writing.
  • Known gaps. Still open from 0.37.0 (checked on main: the JavaScript Mermaid readers still decode #55296; to a
    lone surrogate, a typed view still gets no "listed twice" warning for view.edges, validate() still says nothing of
    a non-string source entry, 21 of the 30 typed examples still do not set "$schema"): a box has no Tab stop; the
    keyboard reaches it through the outline. A double-click (or Enter) on a box does not open its view (the 0.24.0 gap).
    Deep nesting is super-linear outside the core. A composite structure or SysML internal block view's Lines rows name a
    part by its id, not its drawn name. The requirement layout leaves out a link into a box nested more than 64 deep from
    its ranking. Typed hooks that answer Alt+arrows themselves were not checked on views laid out down. reach() from a
    model id that the view draws under another id returns only that element. A negative step duration plays 500 ms while
    validate()'s warning says 4000 ms. Mermaid C4 macro arguments keep entity codes as written. describe() of an
    inline interaction does not say it opens a view. Room for a label in a turned view is still mostly along the line. The
    map flowchart and Structurizr DSL readers turn a U+2028 inside a label into a space. The unfolded call behaviour box
    is a plain container frame. A page rendered before 0.33.0 with a numeric view id, before 0.36.0 with a numeric card
    id, or before 0.37.0 with a view with no id, still ends in a traceback in stills. Three or more delegations from one
    port into a grid of parts may still cross; this needs a routing change. Other files in src/bpmn may still key plain
    objects by id (process.js was checked, and #353 took the prototype off BZ_PIN, BZ_NAME, BZ_TURN and BZ_V). The
    typed Mermaid reader's quote join skips %% comment lines but not the body of a multi-line %%{ }%% directive. The
    PDF tables read an open package's qualified name off its drawn title, and only when the title ends in :: and its
    label. No example reaches the C4 views lift branch or src/sysml/sysml.js's frame branch, so the prototype sweep does
    not check their byId; only select() has a browser test of its own among Find and the panel links. The double-click
    tests send synthetic events. The SysML block definition view has no own list of line kinds, so it draws every kind.
    The SysML tables RQ_REL and BD_ORDER are still plain objects (SYS_IB_PROP, SYS_PAR_PROP and SYS_PAR_SUBJ
    have no prototype). When two operands of one alt each create a lifeline, the second create arrow lands on the stem
    below the single head. printDoc's rules section and rules() still count a typed view's hand-written containers as
    boxes a rule can name. An MCP page tool on a model that has never rendered still says it cannot read the model. New:
    when a delete removes some of several id-less lines with the same ends, the names of the lines left can shift; a name
    that now points at a different line is not caught (only names that no longer exist are cleared). validate() still
    accepts a positional name (docs/diagrams/risks.md F9), and warns only when it names no line. diff() numbers id-less
    lines among id-less lines only, where Ref names count every line with the same ends; the keys never leave diff().
    The profile, package and SysML block definition conformance notes point to the class or package note for the shared
    class rules instead of naming each one.
  • Size: lib/umlimator.js, what a map host loads, is 197.6 kB (197,612 B) with gzip -9, 19.80% over 0.16.0's
    164,954 B, up 1,100 B from 0.37.0, all of it #357 (the line keys in diff(), boxHolds(), the line names and the two
    new warnings). lib/umlimator-all.js is 617.1 kB (617,094 B), up 2,119 B: #357 1,099 B, #354 479 B, #353 309 B and
    #356 232 B; the npm package is 890.5 kB...
Read more

v0.37.0: fixes from the tenth audit

Choose a tag to compare

@github-actions github-actions released this 15 Nov 14:11
0a0fa07

Install: npm install umlimator@0.37.0, or "umlimator": "github:zintaen/umlimator#v0.37.0".

The tenth audit confirmed 24 findings. 23 are fixed in code in this release, in five pull requests (#347 to #351), each
with a test that fails without its fix; the 24th is a slip in the 0.35.0 section, corrected below. No map or example
draws differently and bench/expected.json is unchanged. What changes for callers:

  • Core (#347). apply()'s delete of a card whose id also names a view keeps that view's sub-views' parent: the
    parent is the view, which the delete does not touch (before, the sub-views were detached). A parent that names only
    a card is cleared, as before. A story step's select or highlight entry that is a Ref now names an element:
    references(), delete and hide read its id (a card), its node (a chip or badge) and every one of its ids (a
    line); a container Ref names no element. Delete removes the whole entry, so a line Ref goes when any one of its lines
    goes. validate() now reports a Ref that names nothing as an error, as it already did a plain id; before, it was
    clean. A when, what, how, origin, author or note that is not a string, and a meta.root that is not a
    string, is drawn as text (String()) on the card and in the details panel, and validate() warns " is text:
    drawn as written"; before, render() threw on a list what and the details panel threw on a number author and
    kept showing the previous card.
  • The page (#347). Round 9's double-click drill-down now works inside <umlimator-map>'s shadow root: the host
    document's capture listener tests composedPath(), not contains(), so a double-click opens the card once, and
    Alt+double-click or a double-click on a selected card's name no longer opens the view (a regression in 0.36.0 for
    every element host).
  • UML types (#349). Composite structure: a connector between two ports of one part, or two ports of a subject with
    no box, is not drawn (it was a diagonal) and gets a connector-drawn warning naming the part or the subject; SysML
    parametric and internal block views reuse that picture, so a broken binding with both ends on one value now gets
    that warning next to its binding-ends error. A line typed constructor or toString lays out and is drawn in the
    component, deployment, class, package, use case and composite views, with no function source in its label, accessible
    name, describe() or PDF row (the type-keyed tables have no prototype). PDF: a collaboration role's row is name : Type, with no composite suffix, and a typed view's Boxes table leaves out the hand-written containers the picture
    ignores. The composite palette's Part entry adds a part even when the typed name starts with "port ". Sequence:
    create-once reports a message that reaches a lifeline before its first create in any operand (the head is drawn
    there); a lifeline's stem ends at its last delete unless a later operand still reaches it, and every other delete is
    a cross on the stem (layoutTimeAxis gives an optional stems[].kills).
  • C4, SysML, BPMN and Mermaid (#350). C4 dynamic view with no edges list: a comment link drawn with L or the
    handle is listed and drawn. C4 deployment view whose subject is a software system: the Container instance palette
    entry and T offer only that system's containers ("The view's system has no container to deploy" when it has none); a
    view with no subject still offers every container. Requirement diagram: a Copy that would change the copied text of
    a requirement that already copies one or is copied is refused, in copy-text's words; a Copy between equal texts is
    drawn as before. BPMN: describe() prints a line's and a group's documentation after its name, and the PDF Lines
    table puts a line's documentation after its name. The Mermaid flowchart reader is linear on chained links
    (A-->B-->C-->...): a 105,000-node chain reads in well under 1 s (was about 61 s).
  • CLI (#351). render, diff, drift and the MCP load refuse a view with no id, an empty id or a repeated id in
    one line (views[i].id: a view needs an id, views[i].id "v" is used twice), as validate() does; before, stills,
    check and pdf crashed afterwards. With no Chrome, render prints "checked": false and a "skipped" field with
    the reason, and one stderr line (<out> is written, but its layout check was skipped: no Chrome/Chromium found); it
    still exits 0 (before, it printed "checked": true). diff --base reports a model whose nodes and views are no
    longer both lists as "cannot be read: it is no longer a map model", not as every view and card removed, and counts a
    new model git does not track yet as added. The diff summary puts a word joiner after # and GH- before a digit, so
    #42, owner/repo#7 and GH-12 link no issue.
  • MCP (#348). page_state answers while the model is mid-edit (not JSON) with model.renders: false and the
    error; a page tool on such a version is checked against the last version that rendered, answers "The model no longer
    renders, so the page shows its last version that did: ...", and the open pages get the banner. After a model edit,
    refit() keeps a highlight of a member (a port) and drops an id-less line (a->b#0) the new version no longer has.
  • Correction to 0.35.0. Its CLI (#335) bullet says every < in a page's JSON data block is written <. The CLI
    writes it as the JSON escape \u003c (script_json and data_lt in umlimator.py), the same value once parsed, so a
    rendered page's source shows \u003c wherever a label has <. The 15 Nov 2026 (0.34.0, 0.35.0) entry of
    docs/diagrams/README.md's log has the same slip. The released sections stay as written.
  • Known gaps. Still open from 0.36.0 (checked on main: the JavaScript Mermaid readers still decode #55296; to a
    lone surrogate, a typed view still gets no "listed twice" warning for view.edges, validate() still says nothing
    of a non-string source entry, the 21 typed examples still do not set "$schema"): a box has no Tab stop; the
    keyboard reaches it through the outline. A double-click (or Enter) on a box does not open its view (the 0.24.0 gap).
    Deep nesting is super-linear outside the core. A composite structure or SysML internal block view's Lines rows name
    a part by its id, not its drawn name. The requirement layout leaves out a link into a box nested more than 64 deep
    from its ranking. Typed hooks that answer Alt+arrows themselves were not checked on views laid out down. reach()
    from a model id that the view draws under another id returns only that element. A negative step duration plays 500
    ms while validate()'s warning says 4000 ms. Mermaid C4 macro arguments keep entity codes as written. describe()
    of an inline interaction does not say it opens a view. Room for a label in a turned view is still mostly along the
    line. The map flowchart and Structurizr DSL readers turn a U+2028 inside a label into a space. The unfolded call
    behaviour box is a plain container frame. A page rendered before 0.33.0 with a numeric view id, before 0.36.0 with a
    numeric card id, or before 0.37.0 with a view with no id, still ends in a traceback in stills. Three or more
    delegations from one port into a grid of parts may still cross; this needs a routing change. Other files in src/bpmn
    may still key plain objects by id (only process.js was checked). The typed Mermaid reader's quote join skips %%
    comment lines but not the body of a multi-line %%{ }%% directive. The PDF tables read an open package's qualified
    name off its drawn title, and only when the title ends in :: and its label. No example reaches the C4 views lift
    branch or src/sysml/sysml.js's frame branch, so the prototype sweep does not check their byId; only select() has a
    browser test of its own among Find and the panel links. The double-click tests send synthetic events. The SysML
    block definition view has no own list of line kinds, so it draws every kind. Fixed since 0.36.0: the MCP server's
    refit() no longer keeps any -> string (#348). New: the SysML tables SYS_IB_PROP, SYS_PAR_PROP,
    SYS_PAR_SUBJ, RQ_REL and BD_ORDER were not checked for lookups of Object.prototype names. When two operands
    of one alt each create a lifeline, the second create arrow lands on the stem below the single head (two heads
    cannot be drawn). printDoc's rules section and rules() still count a typed view's hand-written containers as
    boxes a rule can name; changing that changes rule semantics. An MCP page tool on a model that has never rendered
    still says it cannot read the model.
  • Size: lib/umlimator.js, what a map host loads, is 196.5 kB (196,512 B) with gzip -9, 19.13% over 0.16.0's
    164,954 B, up 429 B from 0.36.0, nearly all in #347 (the String() text, the new warnings, the Ref reading) and #349
    (the prototype-free type tables). lib/umlimator-all.js is 615.0 kB (614,975 B), up 1,733 B, most of it #350; the
    npm package is 887.3 kB (npm pack --dry-run). There is no core size cap until 1.0.0 (the maintainer's decision of 15
    Nov 2026): sizes are reported each release and a budget is set at 1.0.0.

v0.36.0: fixes from the ninth audit

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:13
b1bcf10

Install: npm install umlimator@0.36.0, or "umlimator": "github:zintaen/umlimator#v0.36.0".

The ninth audit confirmed 33 findings. All are fixed in this release, in five pull requests (#341 to #345), each with a
test that fails without its fix. 14 of them were one sweep: ids named constructor, toString, valueOf or
__proto__ outside the maps 0.35.0 made prototype-free. No map or example draws differently and bench/expected.json
is unchanged. What changes for callers:

  • Ids named after Object.prototype's keys (#345). Every id-keyed table is now prototype-free where it is built, so
    a card, line, box or view named constructor, toString, valueOf or __proto__ behaves like any other everywhere.
    geo.byId has no prototype in src/layout/layered.js and in every typed layout that builds or copies it (use case,
    timing, sequence, C4, SysML, internal block, parametric, activity, structure's portsDrawn, mind map, the empty
    view), so a prototype name that the view does not draw is no longer "found": no NaN bounds from a box or intake, no
    phantom pick for select(), the live region, Find or a panel link. highlight(), lenses, story steps and the tour
    build their layers the same way and dim such cards and lines; the marks read every layer, a host's plain-object
    overlay() layer included, by own key. diff() keeps the removed, added and changed marks of a card named
    __proto__. A use case actor named __proto__ stays in the actors' column. The PDF Lines table of a typed view no
    longer lists a line named constructor or toString that the view does not draw. A DFD line or a SysML element typed
    with a prototype name no longer gets a function as its end look, word or name, nor makes validate(), layout() or
    check() throw. What a host sees: geo.byId and the highlight and lens layers now have no prototype, so a deep-equal
    against {} differs ([Object: null prototype] {}). apply()'s set refuses __proto__, constructor and
    prototype only as the first key of a path, where they name an element's or view's own field; every deeper key is
    written as an own key, so layout.<id> and present.<id> work for such ids, and no path reaches Object.prototype
    ('__proto__.x' is still refused).
  • Core (#342). mapContext leaves out an entry that is not an object in nodes, edges, views, a view's nodes
    or containers (a null there made layout(), check() and render() throw for every view); validate() already
    reported them as errors. A view's gap or rgap is used only when it is a number above 0, and one over 2000 is drawn
    as 2000; any other value is the default, and validate() warns at views[i].gap / views[i].rgap ("is not a number
    above 0: ignored", "is over 2000 px: drawn as 2000"). Before, 'wide' blanked the view with NaN coordinates. A string
    gap such as '80' is now ignored with that warning (the schema says number); it worked by accident before.
  • The page (#342). A double-click on an unselected card opens it even when the details panel that its first click
    opened moved the legend under the pointer: for about 1 s after a click on a card (same view), render() listens on
    the host document in the capture phase, and a second click or a dblclick outside the map opens the card the first
    click hit; a single click outside clears it, and destroy() removes the listeners. Picking a Find result moves focus
    to the pick (the selected card, or the map for a view) instead of dropping it to <body>.
  • UML types (#343). Class: a view with no edges list draws only class lines (Association, Generalization,
    InterfaceRealization, Dependency, CommentLink; a profile view adds Extension and ProfileApplication), and describe()
    and the line-inside check use the same list. Before, it drew other diagrams' lines (Usage, Connector, Realization,
    PackageImport, InformationFlow and others) as solid filled arrows; list them in view.edges to draw them. Listed, a
    Usage is dashed with an open arrowhead and «use», an Abstraction the same with «abstraction», a Realization or
    ComponentRealization dashed with a hollow triangle, a Connector a plain line, each with a legend entry and its own
    accessible word; a line between two members of one owner is no longer a loop on that owner. Profile: a closed package
    draws the required stereotype its profile supplies (its tags stay in the accessible name). member-kinds now covers a
    profile and a metaclass reference. Component, deployment and composite structure views warn own-boxes when a view
    has hand-written containers, which they ignore. Sequence and communication: create-once and delete-once allow one
    per operand of an alt, as reply-once does, and so does the drag that creates or deletes.
  • SysML, Mermaid and the conformance notes (#341). An internal block view finds a part's type by label ?? id (the
    ports of a block with no label are drawn, no false part-type warning); UML composite structure finds a class with no
    label by its id the same way, and a class with a label by its label only. The parametric binding-types warning names
    a type with no label by its id, not "undefined". writeMermaidClass writes a class named like one of the reader's
    statement keywords (note, class, direction, style and the rest) in backticks, so it reads back. The flowchart,
    state machine and object conformance notes and examples/README.md say what the code does.
  • CLI and MCP (#344). A model with a number id (a card, a line's end, a nodeIds or stepIds entry, a view's
    parent, opensView/view, root) is refused in one line by render, MCP and every command that reads a model
    ("nodes[0].id is not a string"), as validate() says; before, render took it and stills and MCP paths and
    reach crashed. MCP refuses a view's own card whose members is not a list in one line, before highlight hits it.
    check reports a misspelt pack icon on a view's own card. The diff Action's Mermaid sketch writes # as #35;, so a
    label such as "Order #42; paid" reads as written.
  • Known gaps. Still open from 0.35.0 (checked on main: the JavaScript Mermaid readers still decode #55296; to a
    lone surrogate, typed views still get no "listed twice" warning, validate() still says nothing of a non-string
    source entry): a box has no Tab stop; the keyboard reaches it through the outline. A double-click (or Enter) on a
    box does not open its view (the 0.24.0 gap). Deep nesting is super-linear outside the core. A composite structure or
    SysML internal block view's Lines rows name a part by its id, not its drawn name. The JavaScript Mermaid readers still
    decode #55296; to a lone surrogate. The requirement layout leaves out a link into a box nested more than 64 deep
    from its ranking. Typed hooks that answer Alt+arrows themselves were not checked on views laid out down. reach()
    from a model id that the view draws under another id returns only that element. A negative step duration plays 500 ms
    while validate()'s warning says 4000 ms. Mermaid C4 macro arguments keep entity codes as written. describe() of an
    inline interaction does not say it opens a view. Room for a label in a turned view is still mostly along the line. The
    map flowchart and Structurizr DSL readers turn a U+2028 inside a label into a space. validate() gives typed views no
    "listed twice" warning for view.edges (typed views draw the line once). The unfolded call behaviour box is a plain
    container frame. A page rendered before 0.33.0 with a numeric view id, or before 0.36.0 with a numeric card id, still
    ends in a traceback in stills and check. Three or more delegations from one port into a grid of parts may still
    cross; this needs a routing change. Other files in src/bpmn may still key plain objects by id (only process.js was
    checked). The MCP server's refit() still keeps any -> string when it trims a highlight after a model change. The
    typed Mermaid reader's quote join skips %% comment lines but not the body of a multi-line %%{ }%% directive.
    validate() gives no warning for a node's source entry that is not a string. The PDF tables read an open package's
    qualified name off its drawn title, and only when the title ends in :: and its label; a real name field on boxes
    would need tests/core-diet.json recorded again. New: no example reaches the C4 and C4 views lift branch or
    src/sysml/sysml.js's frame branch, so the sweep does not check their byId; Find and the panel links are fixed
    through geo.byId, but only select() has a browser test of its own. The double-click test sends synthetic events; a
    real-mouse sweep of the atlas cards was not run again. The SysML block definition view has no own list of line kinds,
    so it still draws every kind (a Usage there now gets the dashed «use» look). The 21 typed examples do not set
    "$schema".
  • Size: lib/umlimator.js, what a map host loads, is 196.1 kB (196,083 B) with gzip -9, 18.87% over 0.16.0's
    164,954 B, up 897 B from 0.35.0, nearly all in #342 (the entry and gap checks, the double-click listeners, Find's
    focus) and #345 (idTable at every id-keyed table). lib/umlimator-all.js is 613.2 kB (613,242 B), up 1,533 B; the
    npm package is 885.1 kB (npm pack --dry-run). There is no core size cap until 1.0.0 (the maintainer's decision of 15
    Nov 2026): sizes are reported each release and a budget is set at 1.0.0.

v0.35.0: fixes from the eighth audit

Choose a tag to compare

@github-actions github-actions released this 15 Nov 09:54
4def2fa

Install: npm install umlimator@0.35.0, or "umlimator": "github:zintaen/umlimator#v0.35.0".

The eighth audit confirmed 24 findings. All are fixed in this release, in five pull requests (#335 to #339), each with
a test that fails without its fix. No map or example draws differently and bench/expected.json is unchanged. What
changes for callers:

  • Core (#339). A card, box or view whose id is toString, constructor, valueOf or __proto__ lays out like any
    other: before, layout() threw or dropped cards (a hub view with a __proto__ card drew three of its five). Every
    object src/map/context.js, src/canvas/render.js and src/map/validate.js key by a card, box, view or lane id has no
    prototype and is tested with Object.hasOwn, as are the id-keyed maps the same views reach in src/layout/audit.js,
    src/layout/layered.js, src/draw/svg.js and src/map/typed.js. validate() and rules() see such a box or card as any
    other: no false "used twice" error or "in box function toString()…" warning, and a parent: "toString" that names no
    box is an error. A listed model line that ends on another view's box now warns too, and the warning's wording changes
    for the card case as well: "ac" ends on "c", which is not one of the view's cards or boxes: not drawn.
  • The page (#339). Find and the details panel now select boxes. Picking an element this view draws as a box, in the
    Find palette or in the details panel's Comes from, Leads to and Also shown in rows, selects the box (before, nothing);
    Find picks a box on the current view in place, and its hit says "this view" and is ranked as such. go(v, { select })
    and the inner handle's selectId take a box's id the same way; the inner handle gains boxHere(id). Expand, open,
    move and reorder still take a card. The details panel shows a source under meta.sourceBase that holds a bare % as
    written (it threw "URI malformed"), and leaves out a source entry that is not text (source: [42] threw).
  • UML types (#337). Class: an operation whose parameter has a function type ((e: Event) => void, () -> Unit)
    keeps the parameters after it when its row is saved. The PDF's Elements and Lines tables name an open package by the
    qualified name it is drawn with (sales::orders). Composite structure: a card or port with an Object.prototype id
    is sized as any other. Object: a profile is drawn and named as a package with «profile», closed ("Profile
    Persistence (closed)") or open. Timing: a message drawn by keyboard (L) from a lifeline to a change is sent at the
    change's time, not refused as "received before it is sent"; a lifeline end is never sent after the change it reaches
    nor received before the change it leaves, and otherwise the slot's time applies. State machine: F2 on a transition
    and add return { error } for an edit that would add an error (initial-out, fork-join, initial-one,
    history-owner) instead of emitting it. A palette pseudostate now goes into the selected state or region (or a
    state's only region), so a history pseudostate can be added at all; with nothing selected, a second initial or a
    history at the top is refused and the reason is shown (docs/editing.md says so).
  • Flowchart, C4, SysML, cloud and BPMN (#336). writeMermaidFlowchart writes the flows the view draws: its edges
    list (ids resolved, inline flows kept) when it has one, else every flow; a flow it cannot write still gets a
    %% not written line. It writes flowchart LR for every direction the layout draws right, anything but null or
    down (before, only right gave LR). On a C4 dynamic view with no edges list, the first connect adds the
    relationship and lists it as step 1, so it is drawn. SysML type names resolve label ?? id, the name an element is
    drawn with (block labels, the parametric constraint and binding types, internal block interfaces, the property kind
    chosen on add): no false errors for an element with no label. Cloud (AWS, GCP): describe() decides the trademark
    line as layout() does, and an untyped card with an icon reads 'Element ' in describe() and its accessible
    name. writeBpmnXml writes a character XML 1.0 cannot hold (a C0 control such as U+000B, a lone surrogate, U+FFFE,
    U+FFFF) in a label, documentation or id as a space, so the file is well-formed, and reports it once per element
    with status weakened ("a character XML cannot hold: written as a space"; line: '' for the model's title), the
    first weakened item the writer gives. An id so written reads back with the space.
  • CLI (#335). A label or detail holding <!-- and then <script no longer breaks render, diff, drift, the MCP
    page and timelapse: every < in a page's JSON data block is written < (the same value). Every page rendered
    from now on differs from earlier renders in that way; examples/bookshop.html was rendered again and draws the same.
    stills draws a typed view again when another view's id, title or subject changes, and a DFD level when its parent
    view's cards change, as the page's own view key does. A view's own card (view.nodes) gets its icon. diff and
    drift name the user's file, not a deleted temp file, for a malformed model. record says in one line, before it
    looks for Chrome, a story step that is not an object; a tour that is not a list counts as no tour.
  • MCP (#338). tools/call refuses an argument its tool's inputSchema does not list, with a tool error naming it
    and the tool's arguments (reach: no argument direction; its arguments: view, card, backward, depth); before,
    reach with direction: 'backward' silently walked forward. A model with a list or object id gets a tool error
    saying where (the model m.json: nodes[1].id is not a string) from every tool, as render says it, never -32603
    Internal error; validate, which answered on such a model before, now refuses it too.
  • Known gaps. Still open from 0.34.0: a box has no Tab stop; the keyboard reaches it through the outline. A
    double-click (or Enter) on a box does not open its view (the 0.24.0 gap). Deep nesting is super-linear outside the
    core. A composite structure or SysML internal block view's Lines rows name a part by its id, not its drawn name. The
    JavaScript Mermaid readers still decode #55296; to a lone surrogate. The requirement layout leaves out a link into a
    box nested more than 64 deep from its ranking. Typed hooks that answer Alt+arrows themselves were not checked on views
    laid out down. reach() from a model id that the view draws under another id returns only that element. A negative
    step duration plays 500 ms while validate()'s warning says 4000 ms. Mermaid C4 macro arguments keep entity codes as
    written. describe() of an inline interaction does not say it opens a view. Room for a label in a turned view is
    still mostly along the line. The map flowchart and Structurizr DSL readers turn a U+2028 inside a label into a space.
    validate() gives typed views no "listed twice" warning for view.edges (typed views draw the line once). The
    unfolded call behaviour box is a plain container frame. A page rendered before 0.33.0 with a numeric view id still
    ends in a traceback in stills and check. Three or more delegations from one port into a grid of parts may still
    cross; this needs a routing change. Other files in src/bpmn may still key plain objects by id (only process.js was
    checked). The MCP server's refit() still keeps any -> string when it trims a highlight after a model change. The
    typed Mermaid reader's quote join skips %% comment lines but not the body of a multi-line %%{ }%% directive. New:
    the geo.byId that src/layout/layered.js and the typed layouts build with Object.fromEntries still has a
    prototype, so looking up an Object.prototype id that is not drawn there sees the inherited property. validate()
    gives no warning for a node's source entry that is not a string (the page ignores it; the schema forbids it). The
    PDF tables read an open package's qualified name off its drawn title, and only when the title ends in :: and its
    label; a real name field on boxes would need tests/core-diet.json recorded again.
  • Size: lib/umlimator.js, what a map host loads, is 195.2 kB (195,186 B) with gzip -9, 18.33% over 0.16.0's
    164,954 B, up 630 B from 0.34.0, nearly all in #339 (the prototype-free maps and Find reaching boxes) and #337.
    lib/umlimator-all.js is 611.7 kB (611,709 B), up 1,784 B; the npm package is 882.6 kB (npm pack --dry-run). There
    is no core size cap until 1.0.0 (the maintainer's decision of 15 Nov 2026): sizes are reported each release and a
    budget is set at 1.0.0.