Allowed Sub Types in EntryDataExpression #8132
Open
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
skriptlang-automation
bot
added
the
needs reviews
Pesekjak
approved these changes
Aug 16, 2025
Absolutionism
approved these changes
Aug 16, 2025
skriptlang-automation
bot
added
patch-ready
Efnilite
approved these changes
Aug 17, 2025
APickledWalrus
approved these changes
Aug 21, 2025
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.
Problem
Previously, EntryDataExpression used T as the generic parameter for both the default value and the return types, this causes generics issues and didn't allow sub types to be used
Solution
Allow sub types.
Completes: none that i'm aware of
Related: none that i'm aware of