{"version":"2.1.126","anchor":"re-running-an-initialization-step-on-a-code-path","canonical_anchor":"re-running-an-initialization-step-on-a-code-path","heading":"Re-running an initialization step on a code path","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.126\/e\/re-running-an-initialization-step-on-a-code-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.126","markdown":"### Re-running an initialization step on a code path\n\nA second invocation of an internal initialization function was added to a top-level setup block (effectively `OF(); OF();` instead of a single call). This pattern usually indicates a \"the second call ensures X is reset\/applied after some intervening side effect\" fix. There is no user-facing string change associated with it, but it is included here for completeness because it is one of only a handful of non-version-bump structural diffs in this release.\n\n**Evidence**\n\nstructural diff in the `Wh6` initializer adds a duplicate `OF()` call after the existing `OF()` call."}