You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem or limitation you are having in your project
Many nodes require references to resources or other nodes, but it is easy to miss them without a warning.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
A node configuration warning would be shown when an exported variable is not set(and it is not annotated with a ?) while having the flag set to true in the project settings.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
I am unsure of how technical implementation of this would look.
If this enhancement will not be used often, can it be worked around with a few lines of script?
You may override GetConfigurationWarnings, but it's equally easy to forget to do it, and adds boilerplate. This would be ideally be automatically used for all custom nodes.
Is there a reason why this should be core and not an add-on in the asset library?
I believed that it's impossible to do through an add-on.
The text was updated successfully, but these errors were encountered:
Note: [Export] private PackedScene JumpFx = null!; will only be non-nullable, if you have nullable context enabled in your project (in csproj file) or in this file (with #nullable compiler directive).
By default, new Godot projects does not have nullable context enabled. User needs to enable it manually. Related: #8475
Prior to .Net 6, detecting if a reference type is marked as nullabe was cumbersome. (No, Nullable.GetUnderlyingType(type) works for value types only.)
Starting with .Net 6, we have NullabilityInfoContext to check the thing at runtime.
Describe the project you are working on
Mid-sized action platformer.
Describe the problem or limitation you are having in your project
Many nodes require references to resources or other nodes, but it is easy to miss them without a warning.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
A node configuration warning would be shown when an exported variable is not set(and it is not annotated with a ?) while having the flag set to true in the project settings.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
I am unsure of how technical implementation of this would look.
If this enhancement will not be used often, can it be worked around with a few lines of script?
You may override GetConfigurationWarnings, but it's equally easy to forget to do it, and adds boilerplate. This would be ideally be automatically used for all custom nodes.
Is there a reason why this should be core and not an add-on in the asset library?
I believed that it's impossible to do through an add-on.
The text was updated successfully, but these errors were encountered: