Strongly type Resource .tres files in ResourceTree when possible - #201
Open
Seb105 wants to merge 1 commit into
Open
Strongly type Resource .tres files in ResourceTree when possible#201Seb105 wants to merge 1 commit into
Seb105 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resource files can contain type information when they are created from a script which is a GlobalClass/Tool
This PR makes [ResourceTree] search for this information, and where it can, load the resource as that type.
As an example:
Produces this header:
This PR makes the ResourceTree source generator look for
script_class="Type"in types that are found to be a Resource, and use that type where possible.Where script_class is not present or no valid type is found, it is simply treated as Resource.