-
-
Notifications
You must be signed in to change notification settings - Fork 598
Support installing SDK from branch #821
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #821 +/- ##
=======================================
Coverage 92.07% 92.07%
=======================================
Files 54 54
Lines 4933 4933
Branches 1097 1097
=======================================
Hits 4542 4542
Misses 391 391 Continue to review full report at Codecov.
|
README.md
Outdated
@@ -58,6 +58,30 @@ With Parse SDK 2.0.0, gone are the backbone style callbacks and Parse.Promises. | |||
|
|||
We have curated a [migration guide](2.0.0.md) that should help you migrate your code. | |||
|
|||
## Want to ride the bleeding edge? | |||
|
|||
It is recommend to use builds deployed npm for many reasons, but if you want to use |
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.
this first sentence needs some work.
"We recommend using the most recent tagged build published to npm for production. However, you can test not-yet-released versions of the Parse-SDK-JS by referencing specific branches in your package.json
. For example, to use the master branch: ...."
Generated by 🚫 dangerJS |
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.
Docs look good apart from what @acinader already brought up 👍
No description provided.