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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential roundtrip inconsistency with
from_dict().When
usage == PROPERTY_USAGE_NONE, the "usage" key is now omitted from the dictionary. However,from_dict()(lines 106-108) leavesusageat the struct defaultPROPERTY_USAGE_DEFAULTwhen the key is missing. This means:PropertyInfowithusage = PROPERTY_USAGE_NONE→Dictionary→from_dict()→usage = PROPERTY_USAGE_DEFAULTIf roundtrip fidelity is needed, consider updating
from_dict()to default toPROPERTY_USAGE_NONEwhen the "usage" key is absent:Proposed fix to align from_dict() behavior
static PropertyInfo from_dict(const Dictionary &p_dict) { PropertyInfo pi; + pi.usage = PROPERTY_USAGE_NONE; // Match to_dict() behavior when key is missing if (p_dict.has("type")) { pi.type = Variant::Type(int(p_dict["type"])); }🤖 Prompt for AI Agents