Fix PropertyInfo to use hint/usage default constants #1440
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
AThousandShips
added
bug
Naros
force-pushed
the
propertyinfo-wrong-usage-init-value
branch
from
601fdc1
to
e160966
Compare
Naros
changed the title
|
Thanks! |
|
Cherry-picked for 4.1 in PR #1441 |
|
Cherry-picked for 4.2 in PR #1442 |
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.
This seems to stem from the old property usage flags before they were adjusted in 2022. It's probably just best to init the value using the
PROPERTY_USAGE_DEFAULTto avoid this in the future.