Skip to content

Releases: parse-community/Parse-SDK-JS

3.3.2-alpha.1

26 Oct 21:03

Choose a tag to compare

3.3.2-alpha.1 Pre-release
Pre-release

3.3.2-alpha.1 (2021-10-26)

Bug Fixes

  • update parse server dependency branch; recreate package lock (#1424) (38455ef)

3.3.1

24 Sep 22:31
ddea28c

Choose a tag to compare

3.3.1

Full Changelog

Fixes

  • Upgraded crypto-js dependency for compatibility with webpack in Parse Dashboard

3.3.0

12 Jul 16:42
2e7a406

Choose a tag to compare

Improvements

  • Improve support for nested keys (#1364)
  • Doc improvement (#1349)
  • Add npm version ci check (#1345)
  • Added an error code for geospatial index failures (#1342)
  • Added date support to OfflineQuery class (#1344)

Fixes

  • Fix react native build (#1381)
  • Fix weapp uuid error (#1356)
  • Fix EventEmitter undefined on React Native 0.64 (#1351)

3.2.0

09 Apr 14:34
4a75d97

Choose a tag to compare

Breaking Changes

Improvements

  • Allow multiple classNames for Parse.Object.registerSubclass (#1315)
const classNames = ['ClassOne', 'ClassTwo', 'ClassThree'];
for (const className of classNames) {
  Parse.Object.registerSubclass(className, CustomClass);
}

Fixes

  • Fixes build for WeChat WeApp, to reduce package size, see issue/#1331

3.1.0

24 Feb 02:23
7cfc6fb

Choose a tag to compare

Breaking Changes
Parse.Push.send will now return the pushStatusId instead of { result: true }

Features

  • Add Server Health Check Parse.getServerHealth() (#1307)
  • Allow saving with custom objectId Parse.allowCustomObjectId = true (#1309)
  • Parse.Push.send now returns pushStatusId (#1302)
  • Add Parse.Push.getPushStatus (#1302)

Improvements

  • Add modifiers to query.startsWith (#1306)
  • Add modifiers to query.endsWith (#1306)

Fixes

  • EventuallyQueue now polls against /health endpoint, caused 403 forbidden side effect (#1305)
  • Allow nested increment on undefined fields (#1303)
  • Handle increment on nested fields any level deep (#1301)

3.0.0

17 Feb 21:12
e0a4da2

Choose a tag to compare

Breaking Changes
For security purposes, logIn will default to POST instead of GET method. (#1284)

If you need to use GET set the usePost option to false.
Parse.User.logIn('username', 'password', { usePost: false })

Features

  • Add EventuallyQueue API, object.saveEventually, object.destroyEventually (#1291)
  • Add Parse.CLP Object to control ClassLevelPermissions (#1145)
  • Add option { json: true } on queries (#1294)
  • Add IndexedDB Storage Controller (#1297)
  • Add Parse.User.isCurrentAsync() for async storage (#1298)

Improvements

  • Add useMasterKey option to Parse.File.destroy() (#1285)
  • User management on React-Native (#1298)
  • Parse.Schema.addField accepts Pointer and Relation types (#1281)

Fixes

  • Allow connect to LiveQuery with null fields (#1282)
  • fromJSON: Return date if value is type Date (#1293)
  • fromJSON: Allow keys to dirty, allows save fromJSON (#1295)

2.19.0

10 Dec 20:52
897007e

Choose a tag to compare

Features

  • New error code 210 (MFA_ERROR) (#1268)
  • New error code 211 (MFA_TOKEN_REQUIRED) (#1268)
  • New error code 161 (FILE_DELETE_UNNAMED_ERROR) (#1257)

Improvements

  • Parse.File.destroy without name error message (#1257)

Fixes

  • Remove unnecessary object reference and comment from AddUniqueOp (#1253)
  • Internal Referencing for Increment Dot Notation (#1255)
  • Saving for Increment Dot Notation (#1219)

2.18.0

10 Nov 14:24
75d0efa

Choose a tag to compare

Features

  • Support query.findAll() (#1233)

Improvements

  • Pass objects into query.equalTo / query.notEqualTo (#1235)
  • Improving legacy initialization setters/getters (#1237)
  • Remove deprecated backbone options from Parse.Push (#1238)
  • Code Coverage and Unit Tests (#1241)

Fixes

  • Prevent crashing LiveQueryClient if emitter error is not set (#1241)
  • Handle LiveQuery subscription socket error (#1241)
  • Set WeChat socket handlers before connecting (#1241)
  • Parse.Installation validating attribute error (#1241)

2.17.0

07 Oct 21:52
f2673a7

Choose a tag to compare

Improvements

  • User LogIn with usePost option (#1229)

2.16.0

17 Sep 20:57
90191ca

Choose a tag to compare

Idempotency enforcement for client requests. This deduplicates requests where the client intends to send one request to Parse Server but due to network issues the server receives the request multiple times.
(Parse-Server 4.3.0+)
Caution, this is an experimental feature that may not be appropriate for production.

To enable use either of the following:

  • Parse.CoreManager.set('IDEMPOTENCY', true)
  • Parse.idempotency = true

Features

Improvements

  • Allow Pin of unsaved objects in LocalDatastore (#1225)

Fixes

  • crypto-js crashing React Native (#1218)
  • Schema mismatch error on add / remove empty array on Relation (#1222)
  • query.select error on null fields (#1223)