Currently, the #initSwiftExtension macro only registers types at a .scene initialization level. If you need to expose types that run on editor time (e.g. plugin code), you have to resort to the default boilerplate initialization code, and manually register your editor classes:
Considering that this change is dealing with exposing types at different GDExtension.InitializationLevel times, is there any interest in also allowing type registration at .core and .servers levels?
Motivation
Currently, the
#initSwiftExtension
macro only registers types at a.scene
initialization level. If you need to expose types that run on editor time (e.g. plugin code), you have to resort to the default boilerplate initialization code, and manually register your editor classes:Solution
Extending the
#initSwiftExtension
to separately register classes on.editor
init level.Questions
GDExtension.InitializationLevel
times, is there any interest in also allowing type registration at.core
and.servers
levels?