@neocompose/cli 0.34.2 → 0.35.1

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog
 
+## [0.35.1] - 2026-08-19
+
+### Fixed
+
+- Treat `Partial<T>` values as sparse deltas throughout lowering and emission,
+  without invoking or reconstructing `T`'s required constructor.
+- Materialize complete Unity defaults for template-less image and audio
+  registry entries instead of writing an invalid template override shape.
+- Keep declarations inside variant delegate closures out of the global-child
+  registry, so separate `initialize` and `apply` closures may reuse local names.
+
+## [0.35.0] - 2026-08-19
+
+### Added
+
+- P72 expression bodies: write `=> expr;` wherever a body is a single
+  expression — getter-only properties (`bool HasVisited => this.Count > 0;`),
+  an accessor inside a property block (`get => ...;`, `set(int value) => ...;`),
+  functions (`bool Ready(int level) => this.Level >= level;`), and lambdas
+  (`(x) => x * 2`). It is pure sugar: the desugared block compiles to the same
+  instruction stream, and diagnostics point at the authored expression. In a
+  void context the expression is a statement, so it must call or assign; an
+  expression whose value would be discarded is refused with a diagnostic that
+  names the block body as the fix.
+- The `=>` reads as an expression body only where it directly follows a member
+  name or a parameter list's `)`, so a NeoFlow destination arrow after an `=`
+  initializer (`override Trigger Trigger = new(...) => Welcome;`) is unchanged.
+
+### Changed
+
+- `neo pull` and `neo push` canonicalize a stored body to `=> expr;` when its
+  authored spelling is exactly one `return` statement that fits on one line;
+  every other body, and every setter, re-emits as a block. A push preserves the
+  form already on disk for members it did not otherwise rewrite, so authoring a
+  one-line getter in longhand stays byte-identical through a push.
+
+### Fixed
+
+- VS Code highlighting no longer claims the identifier after every `=>` as a
+  NeoFlow destination. The destination scope now requires the NeoFlow shape —
+  an arrow after `)`, a single non-keyword identifier, then `;` — so calls,
+  `this.` chains, types, and `get`/`set` keywords inside expression bodies keep
+  their own scopes.
+
 ## [0.34.2] - 2026-08-19
 
 ### Fixed