-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add cloud function/job calls and user password reset. #43
Conversation
- Also adds more command tests for User and cleans up user docs
Codecov Report
@@ Coverage Diff @@
## main #43 +/- ##
==========================================
+ Coverage 75.73% 76.56% +0.83%
==========================================
Files 32 35 +3
Lines 2724 3239 +515
==========================================
+ Hits 2063 2480 +417
- Misses 661 759 +98
Continue to review full report at Codecov.
|
@TomWFox can you review the docs? @pranjalsatija can you review? |
Conflicts: ParseSwift.xcodeproj/project.pbxproj Sources/ParseSwift/API/API+Commands.swift Sources/ParseSwift/API/API.swift Sources/ParseSwift/API/Responses.swift Sources/ParseSwift/Object Protocols/ParseUser.swift Tests/ParseSwiftTests/ParseObjectBatchTests.swift Tests/ParseSwiftTests/ParseQueryTests.swift
- Added ResultsResponse for explain and hint
…tEmiailVerificaiton
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few minor changes... otherwise LGTM
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
@TomWFox can you add |
… be reverted back
@TomWFox can you look at the documentation I added for the |
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
Co-authored-by: Tom Fox <13188249+TomWFox@users.noreply.github.com>
ParseEncoder
is used for Parse types while json encoder is used for othersbatchLimit
when callingsaveAll
ordeleteAll
ParseObjects
that wasn't being used because it's in a non-working state. It's not needed for now, child objects are sent to the server 1 by 1 until a fix. This may cause more http overhead if there's a lot of unsaved children. I don't see this happening much unless a developer attempts to saveAll "many"ParseObjects
that have "many" unsaved children. In this case,URLSession
and the parse-server should still be able to handle the load. Batching still works forParseObjects
, just not for unsaved children./classes