Tested versions
Test on latest redot beta using the non mono build
System information
Windows 11
Issue description
Expected behavior
When exporting a struct using:
@export var something: MyStruct = MyStruct.new()
the struct should be exposed in the Inspector, allowing its properties to be edited directly.
Actual behavior
The struct can be exported without producing any errors or warnings. However, when the script is attached to a Node, the exported struct does not appear in the Inspector, and none of its properties are displayed or editable.
As shown in the attached screenshot, the exported property is missing from the Inspector entirely.
Example
@export var something: MyStruct = MyStruct.new()
The export is accepted without errors, but something does not appear in the Inspector.
Steps to reproduce
- create project
- create a new script and add a simple struct and export it
- attach it to a node
Minimal reproduction project (MRP)
just create a new project using the latest beta and attach a script.
Tested versions
Test on latest redot beta using the non mono build
System information
Windows 11
Issue description
Expected behavior
When exporting a struct using:
the struct should be exposed in the Inspector, allowing its properties to be edited directly.
Actual behavior
The struct can be exported without producing any errors or warnings. However, when the script is attached to a Node, the exported struct does not appear in the Inspector, and none of its properties are displayed or editable.
As shown in the attached screenshot, the exported property is missing from the Inspector entirely.
Example
The export is accepted without errors, but
somethingdoes not appear in the Inspector.Steps to reproduce
Minimal reproduction project (MRP)
just create a new project using the latest beta and attach a script.