-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Int values are not always recognized. #3
Comments
While the tool itself doesn't do this yet, you can add the type next to the number like so:
This will get the number to be correctly recognized as an integer instead of a string. I came across this issue while using the tool recently, so I tried implementing it (fork). It supports |
Yeah, fortunately that's not too hard if you know that something is not meant to be written as a string. What is an issue, though, is if the command implies that it can be run as-is for non-strings. I just checked out your fork, and it seems to work well for me! I'll probably be using that for now, thanks! 🤩 |
On a second look, it looks like this is trying to establish the type by looking at the serialized value, which I don't think produces correct and secure results. I think using |
Repro on macOS 15.1.1:
plistwatch | grep -v "ContextStoreAgent"
This writes a number to the
plist
, as can be verified by keeping~/Library/Preferences/com.apple.menuextra.clock.plist
open in Xcode.However,
plistwatch
shows e.g.:Running this command will clobber the int value with a string and cause it to be effectively ignored by the OS (in this case).
Although I want to note that
plistwatch
has saved me a lot more time than it has cost me, this particular issue took me a few weeks to really understand and debug before I could fix it for good.The text was updated successfully, but these errors were encountered: