Skip to content

v4.2.2: fix: Resolve change set references regardless of definition order

Choose a tag to compare

@thorewi thorewi released this 23 Sep 04:05
· 1 commit to master since this release
Previously, `$ref` entries in change sets would fail to resolve if their corresponding `$id` definition appeared later in the document. This led to `UnexpectedValueException` and unreadable change log entries.

This change pre-registers all `$id`s found in the document with empty `ChangeSet` instances before decoding begins. This ensures that any `$ref` can find its target instance, allowing for correct resolution even when `$ref` precedes `$id` in the document structure.