-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Refactor pushStatusHandler to use Parse instead of direct access #4173
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4173 +/- ##
==========================================
+ Coverage 92.13% 92.21% +0.07%
==========================================
Files 116 116
Lines 8044 8075 +31
==========================================
+ Hits 7411 7446 +35
+ Misses 633 629 -4
Continue to review full report at Codecov.
|
@@ -127,6 +127,7 @@ describe('Parse.Push', () => { | |||
alert: 'Hello world!' | |||
} | |||
}, {useMasterKey: true})) | |||
.then(() => delayPromise(500)) |
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.
can these be any shorter?
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.
nope, not really, because we don't wait till it's completed...
My intended use? Forward analytics with _PushStatus
Worth noting: when using the experimental direct access, this is pretty much 0 overhead.