-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
fix: improve threading support for .current objects #45
Conversation
Codecov Report
@@ Coverage Diff @@
## main #45 +/- ##
==========================================
- Coverage 90.31% 90.30% -0.01%
==========================================
Files 161 163 +2
Lines 16243 16322 +79
==========================================
+ Hits 14670 14740 +70
- Misses 1573 1582 +9
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
When you try, you can link to tag https://github.com/netreconlab/Parse-Swift/releases/tag/5.0.0-beta.2 Note that there's a small breaking change when initializing the Swift SDK, you can choose add Parse-Swift/ParseSwift.playground/Pages/1 - Your first Object.xcplaygroundpage/Contents.swift Lines 18 to 22 in c7c83f1
|
New Pull Request Checklist
Issue Description
Depending on how
.current
objects are used in an app, crashes can occur due to threading. Close #46Approach
Add a synchronization queue to all
.current
objects.TODOs before merging