Repository navigation
Register the nwc key namespace for NwcIO.Scene - #5
Conversation
mahach666
left a comment
There was a problem hiding this comment.
Reviewed 4d9716a. No actionable findings; ready to merge.
The nwc: registration matches NwcIO.Scene in IOExtend/NwcIO#168: the four keyed tab families, property-name allowlist/patterns and custom-material exclusion agree with the adapter. SourceFormat nwc and owner NwcIO.Scene are consistent. The change is documentation only and follows the existing namespace-registration rules without changing the binary/JSON contract. Independently ran IOScene tests: 239 passed, zero skipped/failed on each of net8.0 and net10.0. Windows/Ubuntu CI is green.
Merge this namespace registration before NwcIO#168 / its first v0.12.0 release, as documented. No merge, tag or publication performed. Submitted as COMMENT because the authenticated account is also this PR's author.
Why
NwcIO.Scene 0.12.0 writes
nwc:keys. Rule 2 ofdocs/keys.mdsays a new producer registers its namespace in the pull request that adds the producer, before its first release. This must be merged before the NwcIOv0.12.0tag.What changes
nwc:row forNwcIO.Scene, formats fixed from 0.12.0; the "no other namespace" sentence no longer names NWC.nwc:section afterifc:with the set keynwc:<TabInternalName>and the property keynwc:<TabInternalName>.<InternalName>.SourceFormattable: thenwcrow namesNwcIO.Sceneas producer (no "later").CHANGELOG.md: a### Changedentry under Unreleased.Checks
Documentation only. Not run: build and tests (no code changes).