Allow post-import plugins to modify _subresources #100792
Open
+32
−26
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.
The old
ResourceImporterScene::import
code fetched some data before theEditorScenePostImportPlugin._pre_process
callback. While the callback could modify existing keys, this prevented users from adding new data on a fresh import.By fetching the keys after pre_process, this means users can consistently modify import options for nodes, meshes, materials and animations in a post-import plugin.
EDIT: Marking it as a bug, because the old behavior was quite inconsistent and I this change doesn't affect any user-facing APIs. If the user had previously opened the advanced importer, then scripts can modify subresources. This change makes it so it always reads the
_subresources
keys after_pre_process
regardless of whether they existed before.