Morphir.Myriad.SystemTextJson.Annotations
0.5.0-alpha.5
Prefix Reserved
dotnet add package Morphir.Myriad.SystemTextJson.Annotations --version 0.5.0-alpha.5
NuGet\Install-Package Morphir.Myriad.SystemTextJson.Annotations -Version 0.5.0-alpha.5
<PackageReference Include="Morphir.Myriad.SystemTextJson.Annotations" Version="0.5.0-alpha.5" />
<PackageVersion Include="Morphir.Myriad.SystemTextJson.Annotations" Version="0.5.0-alpha.5" />
<PackageReference Include="Morphir.Myriad.SystemTextJson.Annotations" />
paket add Morphir.Myriad.SystemTextJson.Annotations --version 0.5.0-alpha.5
#r "nuget: Morphir.Myriad.SystemTextJson.Annotations, 0.5.0-alpha.5"
#:package Morphir.Myriad.SystemTextJson.Annotations@0.5.0-alpha.5
#addin nuget:?package=Morphir.Myriad.SystemTextJson.Annotations&version=0.5.0-alpha.5&prerelease
#tool nuget:?package=Morphir.Myriad.SystemTextJson.Annotations&version=0.5.0-alpha.5&prerelease
Morphir.Myriad.SystemTextJson.Annotations
Attributes and options for Morphir.Myriad.SystemTextJson, a Myriad plugin that generates trim-safe and Native AOT-safe System.Text.Json converters and contexts for F# records, unions and enums at build time.
This package has no dependency and targets netstandard2.0. Nothing in it runs: the generator reads the attributes from the F# source at build time.
open Morphir.Myriad.SystemTextJson
[<JsonUnion(BaseEncoding = (JsonUnionEncoding.InternalTag ||| JsonUnionEncoding.NamedFields), TagName = "kind")>]
type Shape =
| [<JsonName "circle">] Circle of radius: float
| [<JsonName "square">] Square of side: float
| Attribute | Use |
|---|---|
JsonUnion |
The encoding of one union: base encoding and flags, tag and fields names, naming. |
JsonRecord |
The member rules of one record: naming, skippable options, unknown members, null fields. |
JsonName |
The JSON name of a case or field. More names are accepted when reading. |
JsonParsedValue |
A type that is written as text and read only through its parser. |
JsonIgnoreType |
Leave a type out of the context. |
JsonDefaultValue |
A string, Boolean or numeric literal for an absent record member. |
JsonDefaultEmpty |
An empty sequence or map for an absent member. |
JsonDefaultValueProvider |
A direct call to an accessible static method with no arguments, returning the field's type. |
JsonDefaultJson |
An explicit JSON-literal default read through the generated field codec. |
JsonOmitEmpty |
Leave an empty record collection out on writing. |
JsonOmitDefault |
Leave a Boolean record field out on writing when it equals its JsonDefaultValue. |
JsonVersionAlias |
Read one exact legacy member/version pair and normalize it to the current form. |
JsonKnownPaths |
Require every critical path in a string collection to match the exact allowlist. |
Scalar strings are ordinary values, without JSON quoting. Decimal and domain defaults can use JsonDefaultValueProvider(typeof<Defaults>, nameof Defaults.Create); provider code runs only for an absent member at deserialization, and the generated call is checked by the F# compiler. It does not use reflection. Each field can declare only one default. Explicit null retains the field's normal rules.
The generator also supports System.Text.Json's JsonPropertyName and JsonExtensionData attributes; extension data requires a string-keyed JsonElement map record field. Unknown members are preserved beside the named members without a wrapper. New member rules are opt-in; unannotated fields retain their encodings and required-member checks.
The union encodings use the names and meanings of FSharp.SystemTextJson. See the Morphir.Myriad.SystemTextJson guide for the full reference.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen40 was computed. tizen60 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Morphir.Myriad.SystemTextJson.Annotations:
| Package | Downloads |
|---|---|
|
Morphir.Mep
Shared Morphir Extension Protocol messages and transports |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.5.0-alpha.5 | 50 | 11/22/2026 |
| 0.5.0-alpha.4 | 95 | 11/16/2026 |
| 0.5.0-alpha.3 | 104 | 11/14/2026 |
| 0.5.0-alpha.2 | 104 | 11/13/2026 |
| 0.5.0-alpha.1 | 101 | 11/13/2026 |
| 0.4.0-alpha.5 | 95 | 11/13/2026 |
| 0.4.0-alpha.4 | 84 | 11/10/2026 |
| 0.4.0-alpha.3 | 89 | 11/9/2026 |
| 0.4.0-alpha.2 | 54 | 11/8/2026 |
### Added
- `Morphir.Svg` builds immutable SVG scenes with F# computation expressions and C# factories. `Morphir.Diagrams` reads Mermaid flowcharts and sequence diagrams and renders standalone SVG or an offline HTML player in a theme with dark and light palettes: Archify (the default), Monokai, Cobalt, Solarized, Gruvbox, Ocean, Darcula, Material or a custom `DiagramTheme`. `SvgRenderOptions` selects the theme and a mode: `Auto` follows the viewer preference, and `Dark` or `Light` writes one palette. The colours are documented CSS variables that a host page can override. See the [diagram library guide](src/Morphir.Diagrams/README.md) for current coverage.
- `Morphir.Knowledge` provides versioned text selections, annotations and links. `Morphir.Knowledge.Okf` provides an AST and lossless CST with cursor visitors and OKF v0.2 and v0.3 bundle validation through `morphir knowledge validate`. `Morphir.Knowledge.Rdf` provides RDF datasets, graph and statement addresses, and N-Quads exchange. See the [knowledge library guide](src/Morphir.Knowledge/README.md).
- Diagram-linked metadata. Every element of a Mermaid diagram has a stable reference (`DiagramElementRef`, such as `node=Billing` or `edge=Cart/Billing/0`) and an IRI under the diagram's document, and rendered SVG marks each element with `data-ref`. `DiagramSnapshot` and `DiagramSelection` target elements of one source revision, which defaults to the SHA-256 of the source. `DiagramAnnotations` maps comments (W3C Web Annotation) and links to text, code, IRIs or other diagrams to and from RDF, and keeps every other statement. `SvgRenderOptions.WithDocument` and `WithMetadata` embed a dataset canonically in the SVG's `metadata` element as RDF/XML, N-Quads or N-Triples, `DiagramMetadata.TryRead` reads it back, and the offline player marks each annotated element and lists its comments, links and statements in a notes panel. `Morphir.Knowledge.Rdf` adds N-Triples and RDF/XML reading and writing (the W3C RDF/XML suite passes) and RDFC-1.0 canonicalization (the W3C rdf-canon suite passes); `Morphir.Svg` adds namespaced names and a secure metadata reader. XML readers prohibit DTDs and use no resolver. See [Metadata in the SVG](src/Morphir.Diagrams/README.md#metadata-in-the-svg) ([#689](https://github.com/finos/morphir-dotnet/issues/689))
- Every diagram family of diagrams.mbt 60a8dd1. `Morphir.Diagrams` reads Mermaid state, swimlane, architecture (with 526 icon keys: AWS, Azure, Google Cloud and UML symbols copied with their notices, and symbols drawn for this library) and ZenUML diagrams; PlantUML activity (modern and legacy), state, regex, EBNF, JSON and YAML blocks; and BPMN 2.0.2 process and collaboration views with BPMN notation, supplied geometry or an automatic layout. `DiagramSource` detects the language. Each family has element references, themes, the offline player and a printer where the syntax has one (`Mermaid.Print`, `PlantUml.Print`), and the pinned upstream corpora are read as Mermaid and PlantUML read them. Mermaid flowcharts and sequences gain the remaining syntax and canonical printing; connectors take elbow, rounded or curved styles and opt-in bridges; railroad diagrams draw external match traces; and the player explores routes and reachability (`DiagramExploration`) and plays node visits. See the [diagram library guide](src/Morphir.Diagrams/README.md).
- `Morphir.Bpmn` reads BPMN 2.0.2 XML with DTDs and entities refused into a lossless tree and a typed element view, validates structure and references, writes canonical and pretty XML, and traverses and queries the document without recursion. `Morphir.Diagrams.Query` adds a bounded structural query language over trees with a BPMN adapter. `Morphir.Diagrams.Raster` exports the library's SVG as PNG or JPEG and a playback as an animated GIF in managed code, with the same bytes on every platform, embedded Noto fonts under the SIL Open Font License, and player downloads. See [Morphir.Bpmn](src/Morphir.Bpmn/README.md), [Morphir.Diagrams.Query](src/Morphir.Diagrams.Query/README.md) and [Morphir.Diagrams.Raster](src/Morphir.Diagrams.Raster/README.md).
- `DocumentTreeStore.openSnapshot` reads plain v3.1 and v4 JSON or YAML document trees from an `IFileProvider`. Generators can page modules and members and decode selected definitions within a per-file byte limit. The caller keeps the input revision stable while those operations run. See [the pipeline guide](src/Morphir.IR.Pipeline/README.md#read-a-document-tree-by-page).
- The bounded document-tree reader reads contextual trees too: it resolves a name-compaction alias in one typed slot without expanding the enclosing body, in JSON and YAML, and keeps the original bytes for pass-through. It can export one logical file as expanded plain JSON under an output limit that is separate from the source limit, without holding every definition body, and keeps the physical stems that `fileNames` records ([#681](https://github.com/finos/morphir-dotnet/pull/681), [#684](https://github.com/finos/morphir-dotnet/pull/684)).
- `Morphir.Mep` negotiates MEP `0.2.0-draft.2` with model access `0.1.0-draft.1`. A guest can generate from a package on disk without receiving the whole model: `HostSession.CreateWithModelAccess` builds the host, and `StartGenerationAsync`, `AdvanceGenerationAsync` and `CancelGenerationAsync` drive ordered rounds in which the guest requests inventory pages and documents of one snapshot. Deliveries are checked for canonical base64, length, SHA-256, request order and batch limits before dispatch. A draft.1 selection keeps the whole-model path. The same exchange runs on a framed process connection and on a WASM byte-call channel. See [Bounded generation](src/Morphir.Mep/README.md#bounded-generation) ([#680](https://github.com/finos/morphir-dotnet/pull/680), [#684](https://github.com/finos/morphir-dotnet/pull/684)).
- `morphir generate` without `--input` generates from a compile record whose IR is a document tree through a bounded session. The host offers the record's exact IR version and codec under MEP `0.2.0-draft.2`, holds the compile read lease until the guest has stopped, and serves the selected documents without giving the guest the tree's path. It works with a native guest (`--extension`) or an Extism WASM guest configured under `[extensions.<target>]` with `abi = "extism-kernel-v1"`. Frame, guest-state and artifact limits are checked before decoding, and one `maxSessionWorkUnits` budget covers reading and output; running out returns `extension.bounded_work_limit` and discards the stage. Chunks are staged privately, then the completed files go to `<out-dir>/generate/<target>.dest`, are recorded in `<target>.json` and are installed into `--output` through the task record's `installed` ledger. A run that fails after replacing a working result leaves a tombstone, and the previous install stays in place. See [Bounded generation from a compile record](docs/content/docs/cli/generate.md#bounded-generation-from-a-compile-record) ([#690](https://github.com/finos/morphir-dotnet/pull/690), [#691](https://github.com/finos/morphir-dotnet/pull/691), [#697](https://github.com/finos/morphir-dotnet/pull/697)).
- `morphir generate --bounded-profile orders-scale` selects provisional limits for the recorded-tree path with a configured WASM backend and a plain JSON v4 tree, for the Orders scale workload. Its JSON report adds `boundedAccess`: the effective limits, the guest's and Extism kernel's peak linear memory against the applied ceiling, the largest input and output batches, and the discovery index's peak charge. These limits are not a resident-memory guarantee. See [Manual Orders scale admission](docs/content/docs/cli/generate.md#manual-orders-scale-admission) ([#693](https://github.com/finos/morphir-dotnet/pull/693), [#696](https://github.com/finos/morphir-dotnet/pull/696)).
- `Morphir.Files` exchanges trees with `Microsoft.Extensions.FileProviders`: `VFileProviders.asFileProvider` gives a `VFileTree` wherever an `IFileProvider` is accepted, and `VFileProviders.ofFileProvider` builds a tree from any provider (physical, embedded, composite) without reading a file until it is read. `Morphir.Models` now depends on `Morphir.Files`, so the analyzer and MSBuild task folders of `Morphir.Lang.CSharp` also carry `Morphir.Files`, `Microsoft.Extensions.FileProviders.Abstractions` and `Microsoft.Extensions.Primitives`. See [the Morphir.Files README](src/Morphir.Files/README.md#exchange-files-with-ifileprovider).
- `Morphir.Models` has `Morphir.IR.Trees.TreeStems`, the stems of a document tree that `Morphir.Ion` used internally: `escapeName` writes a name as a file stem, `parseStem` reads one back (a whole name or a cut stem), `matchesCut` checks a cut stem's prefix and digest against a name, and `splitDependency` splits a `deps/` path at its bare `@` segment.
- `ClassicJsonWriter` writes a classic `Specs` distribution at format `3.1.0` with the new profile `ClassicWireProfile.v3_1_0`: `"formatVersion": "3.1.0"` and the `Specs` tag. A Specs at 1, 2 or 3, or a Library at 3.1.0, is refused with `unsupported-distribution`, and the message names the supported set. `Morphir.IR.Trees.ClassicDocumentTree`, beside `V4DocumentTree`, splits a classic v3 model into a document tree and joins it back with every attribute unchanged; its manifest records whether the single file says `3` (a Library) or `"3.1.0"` (a Specs).
- `morphir model verify` checks IR v4 and document trees. A single file with `"formatVersion": 4` (or a v4 release such as `"4.0.0"`) is checked against the parent's `morphir-ir-v4.json`, and `--schema-version=4` selects it; it is then decoded with the v4 reader, which names the node at fault in a module (the parent's schema, which checks a module in every spelling, locates the fault only at the module), and the reader's error is listed with its code and JSON location. A directory is a document tree: each file of a v4 tree against its kind in the parent's `morphir-ir-v4-document-tree-files.json`, then every rule of a tree and every document through the document-tree store, as `morphir model convert` reads it; a v3 tree, whose files say `"3.1.0"`, through the store alone. Every error is listed, each with its `file` in the tree and its JSON location (`Path`, a JSON Pointer), and a rule of the tree has the parent's code, such as `missing_member`. The version of a tree comes from its manifest, and a `--schema-version` that contradicts it exits 2 with `verify.schema_version_conflict`. The report adds `layout` (`single-file` or `document-tree`), `filesChecked` and `compactedFiles`, and an error of a tree adds `file` and `code`. See [model verify](docs/content/docs/cli/model-verify.md#document-trees).
- `morphir model convert` stores a Morphir model as a single file or as a document tree without changing the model or its IR version: `morphir model convert --input morphir-ir.json --output tree --layout=document-tree`, and back with `--layout=single-file`. The input's layout is detected (a file or a tree's directory), and `--layout=document-treesingle-file` chooses the output's (the form with a space is accepted too); it defaults to the input's layout, and a run that changes neither the layout nor the encoding exits 2 with `model.nothing_to_do`. IR v3 and IR v4 are converted: a v3 Library tree says `"3.1.0"` in every file and joins back to `"formatVersion": 3`, a v3 Specs keeps `"3.1.0"`, and a v1 or v2 file is refused with `model.unsupported_version`. A tree is read and written through the document-tree store that `model verify` checks trees with, so a refused tree has the parent's code, such as `missing_member` or `tree.ambiguous_profile`, and names its file; a v4 manifest's `version` and `created` are dropped with a `tree.dropped_manifest_member` notice each. `--output` must not exist (a tree may also go to an empty directory) and must not overlap the input (`model.output_not_empty`, `model.output_overlaps_input`); the output is staged beside it and moved into place, so a refused or failed run leaves nothing there. `--json[=streamdocument]` gives the report (`success`, `exitCode`, the paths, layouts and encodings, `irVersion`, `filesWritten`, `diagnostics`, `notices`) and, as a stream, `stageStarted`, `stageCompleted`, `diagnostics`, `notices` and one `fileWritten` event per file. Compacted files are read and written (see the next two entries). See [model convert](docs/content/docs/cli/model-convert.md).
- `morphir model convert` and `morphir model verify` read compacted Morphir files: a single file or a tree file in a name-compaction envelope of finos/morphir's `ir/name-compaction` (`ir-context` 0.1.0-draft.1), whose document names entries of the envelope's `context` with `{"$name": "<id>"}`. The document is expanded at the typed name positions only (classic word arrays in a v3 document, canonical strings in a v4 one, with no change of version), and then read or checked as a plain document. `convert` writes the expanded model plain and states `inputEncoding: "compacted"`; a tree is compacted when any of its files is, so a compacted input with no `--layout` is not `model.nothing_to_do`. `verify` checks the expanded documents against their schemas and lists the compacted files in `compactedFiles`. An envelope or a context that breaks a rule of the contract is refused, naming the file, with the contract's code: `context.undeclared_schema`, `context.unknown_alias`, `context.duplicate_entry`, `context.unknown_critical`, `context.too_many_entries`, `context.name_too_long`, `context.after_document`, `context.invalid_envelope` or `context.invalid_entry` (exit code 1). See [Encodings](docs/content/docs/cli/model-convert.md#encodings) and [Compacted files](docs/content/docs/cli/model-verify.md#compacted-files).
- `morphir model convert --compact[=names]` writes compacted files under finos/morphir's writer policy `morphir.compact/0.1.0-draft.1`: a single file stays one file, and each file of a tree, the manifest included, gets its own context. A name, path or fully qualified name gets an alias only when its uses save more bytes than its table entry costs, and the envelope is written only when the aliases save more than it adds; otherwise the file is its plain document, with a `model.compaction_declined` notice. Every file written with `--compact`, compacted or declined, is in the policy's written form: the member sorting and string escaping of RFC 8785 canonical JSON, no whitespace and no trailing newline, with three exceptions: numbers are written as the plain file writes them (IR v4 keeps their lexemes, so `9007199254740993`, `1.0` and `1e2` stay as they are; a classic v3 float is a double, which the plain file writes in its shortest form, so `1.0` and `1e2` are written `1` and `100`, compacted or not, with the same value), the parameters of a v4 value (a definition's `inputTypes`, a specification's `inputs`) keep their order, and the content of a `DocumentLiteral` is written exactly as in the source, its keys in their order and its numbers as their lexemes. Every size is the UTF-8 byte length of that form. Record fields, module members, constructors and dependencies may come back in sorted order; function parameters keep their order. `Morphir.Json.CanonicalJson.writeSourceForm` writes that form, and `CanonicalJson.write` stays RFC 8785. On Windows, the move of the written output into place, a single file or the staged directory of a tree, waits a bounded time while another process briefly holds a written file open (`Morphir.Files.FileReplacement`, which also counts the access denial that `Directory.Move` raises as an `IOException`), as the publication of a tree's files does; if something appears at the output during the wait, the write is refused with `model.write_failed` and that output is left as it is, never replaced or merged into. The output equals the policy's fixed cases byte for byte, expands to the document it was written from, and is the same for the same model. The report names `compactMode` and `compactPolicy`, and `outputEncoding` is `compacted` when a file written is in an envelope. In `Morphir.Models`, `Morphir.IR.Files.CompactionPolicy.compact` compacts one document, `DocumentTreeStore.write` with `Compact = Some Names` compacts each file of a tree and lists the declined ones in `DocumentTreeStore.plainFiles`, and `StoredModel.TryWriteSingleFile` takes the compaction flag and says whether an alias was worth its cost. See [Compaction](docs/content/docs/cli/model-convert.md#compaction).
### Changed
- `morphir model verify` refuses a single file whose top-level `$schema` is not the declared name-compaction envelope (`ir-context` 0.1.0-draft.1) with `context.undeclared_schema` (exit code 1). It used to check such a file as a plain document. An error in a compacted file is located in the file as written: its `Path` starts with `/document`, the envelope's document member.
- `morphir model verify` lists only the errors of the subschemas that fail: an error of a branch of an `anyOf` or a `oneOf` that another branch satisfies is no longer listed, so an invalid node no longer brings errors of members that are valid. `--schema-version` takes 1 to 4, and another number is a usage error with exit code 2, where it was reported as a file that does not exist. A path whose directory does not exist is reported as a file that does not exist rather than failing.
- **BREAKING:** `morphir model` replaces `morphir ir`. The group holds the commands that act on a Morphir model, and `morphir ir verify` is now `morphir model verify`, with the same inputs, options and exit codes, apart from the changes below and the `--schema-version` entry above. There is no alias: `morphir ir` is an unknown command, so scripts change `ir verify` to `model verify`. The verification report adds `exitCode` (0 valid, 1 not valid, 2 a command line that does not parse) beside `IsValid`, which keeps its name, so the report itself tells a usage failure from a model that is not valid. `--quiet` with a JSON mode now writes the JSON report, which it hid before; `--quiet` alone still writes nothing. See [model verify](docs/content/docs/cli/model-verify.md).
- **BREAKING:** `ClassicWireProfile` replaces `LibraryTag` with `Distribution` (`ClassicProfileDistribution.Library` or `ClassicProfileDistribution.Specs`, each with its tag) and adds `Release`, the string `formatVersion` of a release profile, and `EntryDocs`, how a type or value of a module with no documentation is written. The v1, v2 and v3 profiles write the same bytes as before.
- **BREAKING:** `morphir compile --json` streams: it writes the compile events as JSON Lines (`stageStarted`, `diagnostics`, `stageCompleted`) and ends with one `{"event":"completed","report":{...}}` record that holds the report. `--json=document` writes the report alone, as `--json` did before. `--json-lines` is removed and fails as an unknown option with exit code 2; use `--json`. A mode is given only after `=`: `--json document` fails with exit code 2 and suggests `--json=document`, and the help shows `--json[=streamdocument]`. The conformance `cli` adapter drives `compile --json`.
- **BREAKING:** every other command with machine output follows the same convention: `validate`, `generate`, `config` (`get`, `list`, `show`, `path`, `explain`, `set`, `unset`), `extension list`, `extension runtimes`, `project migrate`, `workspace migrate` and `model verify`. A bare `--json` now writes one `{"event":"completed","report":{...}}` line, which is also one JSON document; `--json=document` writes the report alone, as `--json` did before. A mode is given only after `=`, so `model verify --json model.json` verifies `model.json`, and a mode that is not `stream` or `document` fails with exit code 2. A parse or usage error in a JSON mode still ends with one report and exit code 2: `extension list`, `extension runtimes` and `model verify` now render their own parse errors, with exit code 2 instead of 1. The usage failure of `config` and the migrations adds only the parser messages that quote no value (an unknown mode, the `--json=document` hint, an unknown option name). `extension worker` keeps the form of the pinned WASM worker contract: `--help --json` still writes one `morphir/command-result`, with no `completed` wrapper, and the event lines stay `morphir/command-event`; it takes `--json=stream` and `--json=document`, which change nothing. The conformance runner refuses a host whose help result is wrapped. morphirup's readiness check runs `generate --json=document`. See [Machine output](docs/content/docs/cli/_index.md#machine-output).
- `VFile`, `VFileTree` and `PropertyBag` moved from `Morphir.IR.Pipeline` to the new package `Morphir.Files`, in the namespace `Morphir.Files`. Code that uses them adds `open Morphir.Files` (F#) or `using Morphir.Files;` (C#). `Morphir.IR.Pipeline` depends on `Morphir.Files` and keeps `MorphirProcessor`, so a pipeline also opens `Morphir.IR.Pipeline`.
- `Morphir.Files` writes the nullable metadata of F# nullness, as `Morphir.Models` does, so C# sees which of its values may be null: the delegates of `FileReplacement.Replace` must not be null, and `PropertyBag.Equals` accepts `null`. Before, C# saw every reference type of the package as oblivious and gave no warning for a `null` argument.
### Fixed
- `morphir generate --input <directory>` checks the captured files a second time before decoding. If a file changed or disappeared during capture, it stops with `input-changed` before starting the backend; before, it could generate from a mix of old and new files ([#698](https://github.com/finos/morphir-dotnet/pull/698)).
- `morphir model verify` reports `tree.unreadable_file` with the file name when a document-tree stream fails on close.
- `morphir model convert` no longer drops a member of a classic v3 model that the classic model has no place for, such as a member beside the `inputTypes`, `outputType` and `body` of a value definition, at any depth of a v3 single file or of the `def` or `spec` of a v3 tree file, including a member beside the `access` and `value` of a `def` or the `doc` and `value` of a documented entry (which a tree read refused as `invalid_distribution_shape` at the payload). It refuses the input with `unknown_member` at the member's JSON location (exit code 1, nothing written), and `morphir model verify` reports the same error for a v3 tree, and for a v3 single file that states `"formatVersion": 3` or `"3.1.0"`, which it now also reads with that reader after the schema check. In `Morphir.Models`, `ClassicJson.readDistributionStrict` reads as `readDistribution` does and refuses such a member; `StoredModel.TryReadSingleFile` and the v3 tree reader use it. See [Layouts](docs/content/docs/cli/model-convert.md#layouts).
- `morphir model verify` accepts the v3 `Specs` single file that `morphir model convert` writes. A single file that says `"formatVersion": "3.1.0"` is checked against finos/morphir's 3.1.0 schema (`morphir-ir-v3.json` at `4fa51c8b`, pinned as `morphir-ir-v3.1.0.json`), also with `--schema-version=3`, where the older v3 schema, which accepts the integer `3` and a `Library` only, refused it; the report still says schema version `3`. To pass that schema, `ClassicWireProfile.v3_1_0` writes each type and value of a module that has no documentation as `{ "doc": null, "value": ... }`, the wrapper the 3.1.0 schema requires, where it wrote the bare entry; the new `ClassicWireProfile.EntryDocs` (`ClassicEntryDocStyle.Bare` or `NullDoc`) holds the choice, and the integer 3 profile writes the same bytes as before. See [Schema version detection](docs/content/docs/cli/model-verify.md#schema-version-detection).
- `morphir model convert` writes a document tree that it can read back when a module has a type and a value of one name whose path is over the path budget. Their files now share one cut stem, short enough for the longer `.value.json` path, and the module file's `fileNames` names the name once; before, each file got its own cut stem, `fileNames` held the name twice, and reading the tree failed with `duplicate_member` and `tree.name_mismatch`. finos/morphir's tree specification maps a name to one stem in `fileNames` and does not say how a shared name is cut.
- `ProjectPath.join` keeps an absolute Windows path written with backslashes. `morphir project migrate C:/work/orders` and `config --file C:/work/morphir.toml` no longer read the path as relative to the invocation directory (which `project migrate` reported as `migration.io`).