Releases: parse-community/Parse-SDK-JS
Releases · parse-community/Parse-SDK-JS
6.1.0-alpha.2
6.1.0-alpha.1
6.1.0-alpha.1 (2025-03-05)
Features
6.0.0
6.0.0 (2025-03-02)
Bug Fixes
Parse.Hooks
requests have double forward slash in URL (#2441) (1fc520c)Parse.Query.findAll
not returning all objects with optionjson: true
(#2449) (f160b8c)- Cannot pass
useMasterKey: false
toParse.Cloud.run
(#2431) (abadac9) - Remove validation error handler option
error
from various methods ofParse.Object
(#2445) (52ddaee) - Security upgrade dset from 3.1.3 to 3.1.4 (#2277) (058f8e4)
Features
BREAKING CHANGES
- Internal REST requests for
Parse.Hooks
use a URL that contains a double forward slash, for examplehttp://localhost/parse//hooks/functions
. This release changes the double forward slash to a single forward slash. (1fc520c) - Removes the error handler option
error
fromParse.Object.set
,Parse.Object.setACL
,Parse.Object.unset
,Parse.Role.setName
and instead throws on validation error. Previously, if theerror
option was set, the handler was invoked if a validation error occurred onParse.Object.set
, and if no handler was set, an error was thrown onParse.Object.save
. The new behavior is that an error is thrown atParse.Object.set
. For example, instead of usingParse.Object.set(key, value, { error: ... })
wrapParse.Object.set(key, value)
into atry/catch
block. (52ddaee)
6.0.0-alpha.2
6.0.0-alpha.2 (2025-02-16)
Bug Fixes
BREAKING CHANGES
- Internal REST requests for
Parse.Hooks
use a URL that contains a double forward slash, for examplehttp://localhost/parse//hooks/functions
. This release changes the double forward slash to a single forward slash. (1fc520c)
6.0.0-alpha.1
6.0.0-alpha.1 (2025-02-16)
Bug Fixes
BREAKING CHANGES
- Removes the error handler option
error
fromParse.Object.set
,Parse.Object.setACL
,Parse.Object.unset
,Parse.Role.setName
and instead throws on validation error. Previously, if theerror
option was set, the handler was invoked if a validation error occurred onParse.Object.set
, and if no handler was set, an error was thrown onParse.Object.save
. The new behavior is that an error is thrown atParse.Object.set
. For example, instead of usingParse.Object.set(key, value, { error: ... })
wrapParse.Object.set(key, value)
into atry/catch
block. (52ddaee)