-
-
Notifications
You must be signed in to change notification settings - Fork 876
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat: Remove ParseFacebookUtils
and ParseTwitterUtils
#1779
Conversation
Thanks for opening this pull request!
|
PFFacebookUtils
and `PFTwitterUtilsParseFacebookUtils
and `ParseTwitterUtils
ParseFacebookUtils
and `ParseTwitterUtilsParseFacebookUtils
and ParseTwitterUtils
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1779 +/- ##
==========================================
+ Coverage 64.24% 72.27% +8.03%
==========================================
Files 201 148 -53
Lines 23233 17267 -5966
==========================================
- Hits 14926 12480 -2446
+ Misses 8307 4787 -3520 ☔ View full report in Codecov by Sentry. |
03e1e2b
to
ec3fb42
Compare
Change log entry:
|
# [3.0.0](2.7.3...3.0.0) (2024-04-08) ### Features * Add `PFObject.isDataAvailableForKey` to check if data is available for individual key ([#1756](#1756)) ([dd05d41](dd05d41)) * Remove `ParseFacebookUtils` and `ParseTwitterUtils` ([#1779](#1779)) ([f1311ee](f1311ee)) ### BREAKING CHANGES * Removes convenience modules `ParseFacebookUtils` and `ParseTwitterUtils`, instead manually add the 3rd party authentication service SDK to log in and provide the authentication data to `PFUser.logInWithAuthType` to link the Parse User. ([f1311ee](f1311ee))
🎉 This change has been released in version 3.0.0 |
* commit 'ef9b00de9eeeca7fddfe9439141f5141ff5dac02': (86 commits) chore(release): 3.0.0 [skip ci] ci: Fix release workflow (parse-community#1782) feat: Remove `ParseFacebookUtils` and `ParseTwitterUtils` (parse-community#1779) feat: Add `PFObject.isDataAvailableForKey` to check if data is available for individual key (parse-community#1756) ci: Bump ip from 2.0.0 to 2.0.1 (parse-community#1772) ci: Fix failing CI by pinning bundler version (parse-community#1778) refactor: Remove Carthage dependency (parse-community#1763) refactor: Remove OCMock Carthage dependency (parse-community#1754) ci: Run CI on Xcode 15 and macOS 13 (parse-community#1753) refactor: Update ruby dependencies (parse-community#1752) refactor: Remove framework builder for assets (parse-community#1751) chore(release): 2.7.3 [skip ci] fix: Compilation errors in `ParseLiveQuery` using `Starscream` 4.0.6 (parse-community#1749) docs: Add changelog note about missing assets (parse-community#1750) chore(release): 2.7.2 [skip ci] fix: Compilation errors `Undefined symbol` and `SystemConfiguration not found` on watchOS (parse-community#1748) ci: Remove publishing release assets (parse-community#1745) ci: Fix and build Starter Projects (parse-community#1744) chore(release): 2.7.1 [skip ci] fix: Compilation error on macOS `Undefined symbol: OBJC_CLASS$_PFProductsRequestHandler` (parse-community#1739) ...
@mtrezza , is there any official documentation on how to « add the 3rd party authentication SDK to log in and provide the authentication data to PFUser.logInWithAuthType to link the Parse User » ? According to the front page, the documentation is supposed to be at https://docs.parseplatform.org/ios/guide/ , but in there, the sample code still refers to PFFacebookUtils, which causes Likewise for PFTwitterUtils. |
@mtrezza , In the meantime, I added to my project all |
New Pull Request Checklist
Issue Description
Closes: #1780
Closes: #1775
Closes: #1764
Closes: #1773
Approach
Remove ParseFacebookUtils and ParseTwitterUtils