Nimble
Nimble copied to clipboard
Be more careful about threading and notifications
Make sure that Nimble doesn't try to access notification properties from the main thread as they may have been created on another thread and get upset (most likely when Core Data is involved). Fixes #973
- [x] Does this have tests?
- [ ] Does this have documentation?
- [ ] Does this break the public API (Requires major version bump)?
- [ ] Is this a new feature (Requires minor version bump)?
I'd like to get this in the next release. Approved running the tests here.
This needs some more work and thought on it, and I don't want to gate v10 on it. It's definitely valuable work, but it can also wait until v11.
Thanks for the feedback (wow, 13 days ago), I certainly don't want to dump a PR and run away but it will probably be a little while longer before I can make any further changes FYI.
Bumping this to the next (major?) release in favor of getting async/await support out the door sooner.
Hi John! After a bunch of noodling on this, I forked your fork and made a PR that includes these changes + some feedback: https://github.com/Quick/Nimble/pull/1051
This will get merged shortly. Thanks for being patient!