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
Each OScriptNode performs validation steps when the script is compiled. We've had to relax certain validation requirements, but it would be helpful to enforce these validations to help newusers.
In addition, looking at things like calling void set(StringName, Variant) does not return an error if the property name is not found. We could add specialized Orchestrator settings that would look for this call, specifically validate the property's existence, and throw errors if they don't exist.
Implementation ideas
Introduce a section under Debug or under Orchestrator > Debug where warnings are handled similar to how they're in the standard project settings under Debug > GDScript.
The text was updated successfully, but these errors were encountered:
Description
Each
OScriptNode
performs validation steps when the script is compiled. We've had to relax certain validation requirements, but it would be helpful to enforce these validations to help newusers.In addition, looking at things like calling
void set(StringName, Variant)
does not return an error if the property name is not found. We could add specialized Orchestrator settings that would look for this call, specifically validate the property's existence, and throw errors if they don't exist.Implementation ideas
Introduce a section under Debug or under Orchestrator > Debug where warnings are handled similar to how they're in the standard project settings under Debug > GDScript.
The text was updated successfully, but these errors were encountered: