Releases: yulcat/unity-yaml-bridge
v1.0.6
Bugfix release for path-based references to root components inside nested prefab instances.
Highlights
- Support
->Path:Componentreferences to components attached directly to the ROOT GameObject of a nested prefab instance - Resolve stripped nested-root MonoBehaviours through their source prefab when local stripped docs do not expose enough type information
- Keep the fix conservative to nested prefab ROOT components rather than broad arbitrary deep internals
Validation
npm testpassing onmastertest-path-refsregression coverage added for nested prefab root refsnode dist/cli.js --versionverified as1.0.6
Included issue coverage
- #5 Support -> references to components inside nested prefab instances
v1.0.5
Bugfix release for STRUCTURE component enumeration when MonoBehaviour ownership is only recoverable from the GameObject component list.
Highlights
- Fix missing
SimpleFSMController-style components in STRUCTURE when the component document'sm_GameObjectreference is zero/broken but the owningGameObjectstill references it inm_Component - Apply the same fix to inherited variant STRUCTURE output
- Add default regression coverage for both base-prefab and variant cases
Validation
npm testpassing onmastertest-variant-issues: 38/38node dist/cli.js --versionverified as1.0.5
Included regression coverage
- base prefab: component-list-only MonoBehaviour ownership preserved in STRUCTURE
- variant: inherited base component-list MonoBehaviour preserved in STRUCTURE
v1.0.4
Bugfix release for nested non-root PrefabInstance write-back.
Highlights
- Fix edited
DETAILSsections for non-root nestedPrefabInstanceinternals writing back to the wrong place or not writing back at all - Fix edited nested internal objectReference path refs (
->Target:Component) writing back through the correct owning nested instance - Strengthen default regression coverage so nested internal visibility alone is no longer treated as sufficient
Validation
npm testpassing onmastertest-variant-issues: 34/34node dist/cli.js --versionverified as1.0.4
Included regression coverage
- nested internal component header + REFS ownership exposure
- edited nested internal scalar property write-back
- edited nested internal objectReference path write-back
- wrong-owner guardrail (root instance must not be edited when nested section changes)
- previously fixed added-root / variant write-back coverage remains green
v1.0.3
Bugfix release for variant added-object reference normalization.
Highlights
- Fix write-back for mixed
__added_root__/ non-prefixed paths in variant-added object references - Handle the same aliasing rules across section matching, scalar refs, array refs, nested refs, and added-section lookup
- Keep emitted variant-added
DETAILSrefs in the canonical non-prefixed form - Preserve
ubridge --versionsupport for install verification
Validation
npm testpassing onmastertest-variant-issues: 25/25investigations/issue3-added-root-refs.js: 8/8node dist/cli.js --versionverified as1.0.3
Included follow-up coverage
- scalar
->__added_root__/...with non-prefixedREFS - array
->__added_root__/...with non-prefixedREFS @__added_root__/...alias resolution- prefixed
DETAILSsection header + non-prefixedREFS - no-edit parse → write roundtrip stability for mixed-prefix compact files
v1.0.2
Follow-up bugfix release for variant write-back and CLI verification.
Highlights
- Fix write-back for references edited inside real added-object component docs in variant files
- Support both normal added-object paths and
__added_root__/...reference paths - Add
ubridge --version/ubridge -vfor quick install verification
Validation
npm testpassing onmastertest-path-refs: 21/21test-variant-issues: 11/11node dist/cli.js --versionverified
Covers follow-up to issue #3 after the v1.0.1 repro report.
v1.0.1
Bugfix release for variant prefab support and write-back reference resolution.
Highlights
- Fix variant
STRUCTUREoutput so root-level added GameObjects are preserved and shown with+markers - Surface nested PrefabInstance overrides in variant
DETAILS/REFS - Fix write-back so newly edited
->Path:Componentreferences resolve againstREFS, including variant object references that originally started as{fileID: 0} - Add focused regression suites for variant edge cases and path-reference write-back
Validation
npm testpassing onmastertest-path-refs: 21/21test-variant-issues: 8/8
Included issue coverage