You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just as major iOS versions deprecate, or introduce functionality, Parse JS SDK is also seeing backward breaking changes as well as new functionality. For instance, the Parse.Promise.when behaviour introduced in 1.7 will break code targeting 1.6.14 (e.g. #95).
Users have no say in when Cloud Code gets upgraded, so while developers like me build code against 1.7.0-rc, we must expect to deploy to 1.6.14. How can I write an if statement to help my code transition gracefully from one version to the next?
The text was updated successfully, but these errors were encountered:
@fatuhoku when we release new versions of the SDK, they aren't automatically used for your cloud code apps. When you first create a cloud code app, it will use the latest JS SDK version available, and it will remain at that version unless you explicitly change it. You're in full control, using the parse CLI.
When you call parse jssdk, it shows you the SDK version your app is using. parse jssdk --all shows all available versions. parse jssdk X.Y.Z will set your cloud code app to use version X.Y.Z
If you really need to access the version string, it's available at Parse.CoreManager.get('VERSION'). We don't make it easily accessible, to avoid users gating behavior on the version number, which is a risky pattern.
Just as major iOS versions deprecate, or introduce functionality, Parse JS SDK is also seeing backward breaking changes as well as new functionality. For instance, the
Parse.Promise.when
behaviour introduced in 1.7 will break code targeting 1.6.14 (e.g. #95).Users have no say in when Cloud Code gets upgraded, so while developers like me build code against
1.7.0-rc
, we must expect to deploy to1.6.14
. How can I write anif
statement to help my code transition gracefully from one version to the next?The text was updated successfully, but these errors were encountered: