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
A developer should be able to search for an Orchestration by its filename, much like an unnamed GDScript class and to view its associated documentation like other script languages, i.e.:
Implementation ideas
This requires four changes:
OScriptLanguage::get_type() should return OScript::get_class_static() rather than Orchestrator.
The language's icon should be registered with OScript::get_class_static() in plugin.cpp.
OScriptLanguage::_supports_documentation() should return true.
OScript::_get_documentation() should return the documentation metadata.
The text was updated successfully, but these errors were encountered:
Description
A developer should be able to search for an Orchestration by its filename, much like an unnamed GDScript class and to view its associated documentation like other script languages, i.e.:
Implementation ideas
This requires four changes:
OScriptLanguage::get_type()
should returnOScript::get_class_static()
rather thanOrchestrator
.OScript::get_class_static()
inplugin.cpp
.OScriptLanguage::_supports_documentation()
should returntrue
.OScript::_get_documentation()
should return the documentation metadata.The text was updated successfully, but these errors were encountered: