UserDefaults.didChangeNotification
triggers for any kind of user defaults change in the process. Even for included SDK or even Apple's APIs. This makes it both inefficient and dangerous. I just had an infinite loop where I was listening to UserDefaults.didChangeNotification
and in the handler, it was setting button.imagePosition
and apparently setting that properly causes a userdefault to be set internally, which resulted in an infinite loop.
I think it would be better to only listen to the keys we know about.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too