Expose EditorExport
through the EditorInterface
singleton
#98251
+124
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exposes
EditorExport
through theEditorInterface
singleton. Also exposes functions relating to feature tags of platforms and presets, similar to the existingEditorExportPreset.get_custom_features()
function.Background
Many properties of
EditorExportPlatform
EditorExportPreset
and have been exposed in #90782, but it is currently not possible to iterate through these in some types of editor plugins and tools. Many of the newly exposed properties could be used in editor tools, such as my Resource Remaps plugin, which loads custom and platform feature tags.Related PRs
Feature tags in scripting: #86747
Implementation
I have kept the scripting API similar to the C++ API, but that does mean there are some style differences between getting custom features (existing function that returns a comma delimited
String
) and getting the platform/preset features (new functions that return aTypedArray<String>
).