uxml-preview 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -1,6 +1,79 @@
 # Changelog
 
-## 0.3.0 — Unreleased
+## 0.4.0 — 2026-08-12
+
+### Added
+
+- The Unity golden dumper can run from the command line, records the Unity
+  revision, editor scale, accessible font settings, and timestamp beside each
+  measurement, rejects `-nographics` and `-quit` up front, and exits non-zero
+  unless it writes exactly one JSON file per discovered case.
+
+### Changed
+
+- Relative `@import` requests are deduplicated by `(url, from)`, matching Unity's
+  parent-relative loading. Root-fixed imports (`project://…` or a path beginning
+  with `/`) are globally deduplicated, and nested `<Style>` attachments now keep
+  their Unity subtree scope. The rule comes from five Unity measurement cases,
+  including the otherwise surprising split between `Packages/...` (relative)
+  and `/Packages/...` (root-fixed).
+
+- **Issue #1: `resolveImport` now receives a second argument,
+  `from: string | null`** —
+  the URL of the stylesheet containing the import being resolved, `null` for
+  a `<Style src="…">` reference. Without it, a relative `@import` inside an
+  imported sheet was unresolvable in principle: `a.uss` importing `"b.uss"`
+  means a path relative to `a.uss`, and the host had no way to learn `a.uss`'s
+  own URL at the point it resolved `b.uss`. `from` is always the exact string
+  this hook received as `url` for the containing sheet, never reconstructed —
+  matters most for nested imports, where it is the immediate parent, not the
+  original sheet. **Non-breaking**: existing one-argument callbacks keep
+  working unchanged, same as `resolveAsset`'s `form` argument in 0.3.0.
+- With this, `resolveImport` joins `resolveAsset` at two positional arguments.
+  Per the "코어에 무언가를 더하기 전에" rule in CLAUDE.md, the next argument
+  either hook would need is the point to switch to an options object instead
+  of adding a third positional one.
+
+### Fixed
+
+- **Issue #2: inline `style="…"` asset URLs reach `resolveAsset`
+  XML-entity-decoded**,
+  matching what a `<Style src>`-loaded `.uss` file's URLs already got (that
+  file was never XML, so it never had entities to decode; an inline attribute
+  is XML text and did). `background-image: url('…&guid=…')` written inline
+  used to reach the hook as `&apos;…&amp;guid=…&apos;` — wrapper quotes and
+  ampersands both literal — because `inlineDeclarations` (style/resolve.ts)
+  parses straight from the raw XML source. Fixed at `assetPath()`
+  (render/css-map.ts), immediately before the `url()`/`resource()` wrapper is
+  parsed and right before the value leaves the model for the hook — the same
+  point `<Style src>` and painted text already decode at, not at parse time
+  (decoding then would corrupt the byte-exact round-trip source slices).
+  Confirmed against two real URLs from the external corpus in
+  `ReuHomi/vscode-uxml-preview` (`examples/external`, commit `dbda387`) where
+  this caused `asset-unresolved` for 7 URLs across 2 files. Scope: only the
+  asset-URL value reaching `resolveAsset`; other inline-style property values
+  still carry undecoded entities in the model (unaffected here, since no
+  other current consumer inspects their text — `-unity-font-definition`'s
+  `resource(...)` value is only checked for presence, never read).
+
+### Docs
+
+- **`docs/accuracy.md`'s "which controls this covers" table now has a stated,
+  computed rule** instead of being left unverified. It never added up on its
+  own terms (17+1+6+5+1 = 30, not the stated 31) and the original counting
+  rule was never written down, so it is now defined explicitly — classify
+  `inventory` as the representative screen, then each other case by the first
+  of `<ui:ScrollView`, `<ui:Button`, `<ui:Label` its UXML contains, else
+  `VisualElement` only — and computed from `tests/golden/cases.ts` rather than
+  hand-counted. Updated numbers: `Button` 6→10, `ScrollView` 5→4 (`VisualElement`
+  only, `Label`, and the representative screen are unchanged). Mirrored into
+  `docs/accuracy.en.md`, which is not machine-checked.
+- **The drift guard now covers this table's five numbers too**, in
+  `docs/accuracy.md` only. Same shape as the three headline figures: recomputed
+  live and failing (not skipping) if it can't find a row to check. Confirmed by
+  breaking a count and by removing a row's label, both on purpose.
+
+## 0.3.0 — 2026-08-09
 
 Four fixes the VSCode extension (`vscode-uxml-preview`) hit while consuming
 this package as a dependency — not speculative additions.

package/README.md

@@ -47,8 +47,8 @@ directly in a web browser. It uses **Yoga** — the same layout engine Unity UI
 itself uses — compiled to WebAssembly, so results match the Unity Editor rather than
 approximating it.
 
-Measured against Unity 6000.0.40f1: **548 of 564 element coordinates identical**
-across 33 layout cases, including a full working screen. Ten of the sixteen
+Measured against Unity 6000.0.40f1: **660 of 676 element coordinates identical**
+across 40 layout cases, including a full working screen. Ten of the sixteen
 differences are font metrics rather than layout — a browser cannot measure
 Unity's font asset. All sixteen are named in
 [`docs/accuracy.en.md`](docs/accuracy.en.md).
@@ -210,12 +210,12 @@ Checked by comparing element geometry against the Unity Editor, case by case.
 Geometry rather than pixels: Unity draws text with its own font asset and a
 browser does not, so a pixel diff would measure the font more than the layout.
 
-Measured against Unity on 2026-08-06, over 33 cases and 141 elements:
+Measured against Unity on 2026-08-12, over 40 cases and 169 elements:
 
 | | |
 |---|---|
-| Cases matching exactly | **31 / 33** |
-| Values within 0.5px | **548 / 564 (97.2%)** |
+| Cases matching exactly | **38 / 40** |
+| Values within 0.5px | **660 / 676 (97.6%)** |
 
 The sixteen divergences are four different things, and the distinction matters
 more than the ratio: **ten are text metrics**, three are 1px, two are a
@@ -246,7 +246,7 @@ as nested flex, and computed values have to be resolved to fixed numbers or
 calculated in C#.
 
 **How close is the output to Unity?**
-548 of 564 element coordinates identical against Unity 6000.0.40f1, across 33
+660 of 676 element coordinates identical against Unity 6000.0.40f1, across 40
 layout cases including a complete inventory screen. Geometry is compared rather
 than screenshots, because Unity draws text with its own font asset — which is
 also why ten of the sixteen differences are font metrics rather than layout.
@@ -280,8 +280,8 @@ Apache-2.0
 **Yoga**를 WebAssembly로 그대로 사용하기 때문에, 결과를 "비슷하게 흉내내는" 것이 아니라
 유니티 에디터와 일치시킵니다.
 
-Unity 6000.0.40f1과 대조한 결과, 실무형 화면을 포함한 레이아웃 케이스 33개에서
-**요소 좌표 564개 중 548개가 일치**합니다. 어긋난 16개 중 **10개는 레이아웃이 아니라
+Unity 6000.0.40f1과 대조한 결과, 실무형 화면을 포함한 레이아웃 케이스 40개에서
+**요소 좌표 676개 중 660개가 일치**합니다. 어긋난 16개 중 **10개는 레이아웃이 아니라
 폰트 메트릭** 차이입니다 — 브라우저는 유니티 폰트 에셋을 잴 수 없습니다.
 16개 전부 [`docs/accuracy.md`](docs/accuracy.md)에 이름과 사유를 적어뒀습니다.
 
@@ -414,8 +414,8 @@ pnpm build
 계산이 필요한 값은 고정값으로 풀거나 C#에서 계산해야 합니다.
 
 **유니티와 얼마나 같나요?**
-Unity 6000.0.40f1 기준, 인벤토리 화면 전체를 포함한 레이아웃 케이스 33개에서
-**요소 좌표 564개 중 548개 일치**입니다. 스크린샷이 아니라 좌표를 비교하는데,
+Unity 6000.0.40f1 기준, 인벤토리 화면 전체를 포함한 레이아웃 케이스 40개에서
+**요소 좌표 676개 중 660개 일치**입니다. 스크린샷이 아니라 좌표를 비교하는데,
 유니티가 자기 폰트 에셋으로 글자를 그리기 때문입니다 — 그리고 그 사실 때문에
 불일치 16개 중 **10개가 레이아웃이 아니라 폰트 메트릭**입니다. 전부
 [`docs/accuracy.md`](docs/accuracy.md)에 이름이 적혀 있습니다.

package/dist/index.d.ts

@@ -37,8 +37,23 @@ export interface ParseOptions {
      * `project://database/Assets/UI/base.uss`, which only the host application
      * knows how to turn into file contents, and there is no reason for a host to
      * implement that lookup twice.
+     *
+     * `from` is the URL of the stylesheet containing this import — exactly the
+     * string this hook received as `url` when that containing sheet was itself
+     * resolved, unmodified. `null` for a `<Style src="…">` reference, which is
+     * not contained in any stylesheet. A relative `@import` cannot be resolved
+     * without this: `a.uss` importing `"b.uss"` means a path relative to `a.uss`,
+     * not to the UXML document, and there is no other way for the host to learn
+     * `a.uss`'s own URL at the point it resolves `b.uss`.
+     *
+     * Non-breaking: this is an added argument, not a replacement one, so an
+     * existing one-argument callback keeps working unchanged.
+     *
+     * Relative imports are deduplicated by `(url, from)`, so two parent sheets
+     * may resolve the same spelling to different files. Root-fixed URLs —
+     * `project://…` or a path beginning with `/` — are deduplicated by URL alone.
      */
-    resolveImport?: (url: string) => string | null;
+    resolveImport?: (url: string, from: string | null) => string | null;
 }
 export declare function parse(uxml: string, uss?: string, options?: ParseOptions): UxmlDocument;
 /**