[feat] File exclusion in structure loaders #97
Merged
Conversation
This file contains 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.
Description
This PR simply adds a flagger to the structure loader for file exclusion. In any file that utilises a structure loader predicate, simply export
__loader_excludewith the booleanTrueto exclude it from the loading process.Why is this useful?
In structures where multiple files may be used to store code for a single structure (i.e. callsystems), having a loader exclusion flag could be very important if the structure being exported potentially meets the conditions for the predicate.
i.e. Say that you have a callsystem, but you also call a second class that happens to also be a Callsystem subclass. Having the structure loader attempt to load it when it shouldn't could cause severe consequences, including glitches and a full crash.