Skip to content

Comments

Ensure schematics manager is initialised on reloads#2896

Merged
me4502 merged 1 commit intoversion/7.4.xfrom
fix/init-schematics-manager-on-reload-too
Jan 21, 2026
Merged

Ensure schematics manager is initialised on reloads#2896
me4502 merged 1 commit intoversion/7.4.xfrom
fix/init-schematics-manager-on-reload-too

Conversation

@me4502
Copy link
Member

@me4502 me4502 commented Jan 21, 2026

Move the init point of the schematics manager to the reload configuration event, running uninit before the actual init to make sure that it's adequately cleaned up. uninit is safe to run when not yet initialised, as it checks before cleaning anything up.

This also ensures that fallback schematic systems are initialised late enough to obtain necessary data.

This should fix issues such as #2895 with filesystems that need to fallback, as well the fact that reloading does not apply schematic folder changes (albeit without an issue number as it's not been reported)

@me4502 me4502 requested a review from a team as a code owner January 21, 2026 10:31
@me4502 me4502 added this pull request to the merge queue Jan 21, 2026
Merged via the queue into version/7.4.x with commit 6118167 Jan 21, 2026
5 checks passed
@me4502 me4502 deleted the fix/init-schematics-manager-on-reload-too branch January 21, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants