Repository navigation
Preserve full 64-bit integer values when editing and verifying plists - #31
Merged
Merged
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.
Integer editing currently rejects plist values above Int64.max even though binary property lists can represent the full UInt64 range. The read-back comparison also truncates NSNumber values through int64Value, so UInt64.max can compare equal to -1.
This change parses the signed and unsigned 64-bit ranges explicitly and compares integer values by their full decimal representations. It preserves the existing Boolean and floating-point handling.
Validation:
Device cache writes were tested through the existing test writer; no physical-device write is claimed.