status-im
/
realm-js
mirror of https://github.com/status-im/realm-js.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
realm-js/CHANGELOG.md

385 lines
12 KiB
Markdown
Raw Normal View History

[1.10.0] Bump version
2017-07-12 14:45:35 +00:00
1.10.0 Release notes (2017-7-12)
Rethrow callback errors as fatal Node.js errors Instead of rethrowing the JavaScript error emitted from a callback function, we should instead pass it to `node::FatalException`. Callbacks are employed when there is no other JavaScript frame on the stack prior so rethrowing the JS error as a C++ exception is not going to propagate the error back to JavaScript. `node::FatalException` will raise the `uncaughtError` event on the `process` object , print the error and stacktrace, and alert the debugger is there is one attached. This would make our async callbacks behave consistently with Node’s own async callbacks such as `setTimeout` when encountering an error.
2017-07-11 11:17:41 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
Add `Realm.empty`
2017-07-12 11:02:21 +00:00
* Added `Realm.prototype.empty` which is a property that indicates whether or not the realm has any objects in it.
Rethrow callback errors as fatal Node.js errors Instead of rethrowing the JavaScript error emitted from a callback function, we should instead pass it to `node::FatalException`. Callbacks are employed when there is no other JavaScript frame on the stack prior so rethrowing the JS error as a C++ exception is not going to propagate the error back to JavaScript. `node::FatalException` will raise the `uncaughtError` event on the `process` object , print the error and stacktrace, and alert the debugger is there is one attached. This would make our async callbacks behave consistently with Node’s own async callbacks such as `setTimeout` when encountering an error.
2017-07-11 11:17:41 +00:00
### Bug fixes
* Fix crash on Node.js when a listener callback throws an error.
The error will now be forwarded to Node's fatal error handling facilities. This means better error reporting,
the ability to debug such errors in a Node.js debugger, and proper invocation of the `uncaughtError` event on the `process` object.
[1.9.0] Bump version
2017-07-10 15:26:44 +00:00
1.9.0 Release notes (2017-7-10)
Add support for accessing linking objects / backlinks (#1101) * Add support for linkingObjects * Test linkingObjects * Borrow names helper from list tests * include computed properties when serializing the schema for the RN debugger * add API docs * review comments * Expose admin users to JS (#1100) The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct. #1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user. * [1.8.3] Bump version * add linkingObjects method to Realm.Object * changelog
2017-06-29 09:59:10 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
[1.9.0] Bump version
2017-07-10 15:26:44 +00:00
* Add support for iOS React Native 0.46. Thanks [@ovr](https://github.com/ovr)!
Add support for accessing linking objects / backlinks (#1101) * Add support for linkingObjects * Test linkingObjects * Borrow names helper from list tests * include computed properties when serializing the schema for the RN debugger * add API docs * review comments * Expose admin users to JS (#1100) The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct. #1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user. * [1.8.3] Bump version * add linkingObjects method to Realm.Object * changelog
2017-06-29 09:59:10 +00:00
* Add support for Linking Objects (AKA Backlinks).
Docs for retrieveAccount method (#1127) * Docs for retrieveAccount method * fix setTimeout call
2017-07-08 17:30:25 +00:00
* Add support for retrieving user account information.
Add a new optional server parameter to User.adminUser (#1111) * add a new optional server parameter to User.adminUser This enables `User.openManagementRealm()` for admin token users. * changelog * API docs
2017-07-10 13:04:55 +00:00
* Add optional `server` parameter to `Realm.Sync.User.adminUser`
Specifying the server address the same way as in `Realm.Sync.User.login` allows the admin token user to use the permission realm APIs.
Add support for accessing linking objects / backlinks (#1101) * Add support for linkingObjects * Test linkingObjects * Borrow names helper from list tests * include computed properties when serializing the schema for the RN debugger * add API docs * review comments * Expose admin users to JS (#1100) The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct. #1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user. * [1.8.3] Bump version * add linkingObjects method to Realm.Object * changelog
2017-06-29 09:59:10 +00:00
### Bug fixes
Make it possible to assign a List or Results to a List property once more (#1126) * Make it possible to assign a List or Results to a List property. The change made in #1069 to improve error messages when values of incorrect types were assigned to a given property was being too narrow in the types it accepted for list properties, allowing only arrays. Lists and Results are now accepted once more. * Update CHANGELOG.md
2017-07-10 11:45:49 +00:00
* Fix regression where setting a Results or List object to a `list` property would throw.
Add support for accessing linking objects / backlinks (#1101) * Add support for linkingObjects * Test linkingObjects * Borrow names helper from list tests * include computed properties when serializing the schema for the RN debugger * add API docs * review comments * Expose admin users to JS (#1100) The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct. #1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user. * [1.8.3] Bump version * add linkingObjects method to Realm.Object * changelog
2017-06-29 09:59:10 +00:00
[1.8.3] Bump version
2017-06-27 18:38:39 +00:00
1.8.3 Release notes (2017-6-27)
Expose admin users to JS (#1100) The JS binding used to conflate `SyncUser::is_admin()` with the user being created by calling `Realm.Sync.User.adminToken()`, but now that we expose a user’s role on the server under `is_admin()` this supposition is no longer correct. #1097 attempted to fix one such case, but fixing it only uncovered another: in `UserClass<T>::all_users()`. I’ve gone through all the callsites of `SyncUser::is_admin()` to make sure they don’t assume an admin token user.
2017-06-27 18:32:34 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bug fixes
* Fix admin users not appearing in `Realm.Sync.User.all`, which broke getting an access token for them.
[1.8.2] Bump version
2017-06-26 11:49:50 +00:00
1.8.2 Release notes (2017-6-26)
Fix refreshing the access token of a logged-in admin user (#1097) Fixes #1091
2017-06-26 10:03:48 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
Added method to find index of object in collections (#1094) * Added method to find index of object in collections * rework as the indexOf method
2017-06-26 11:43:49 +00:00
* Added `indexOf()` method on `Realm.Results` and `Realm.List` that returns the index of the object in the collection.
Fix refreshing the access token of a logged-in admin user (#1097) Fixes #1091
2017-06-26 10:03:48 +00:00
### Bug fixes
* Fix opening synced realms with a logged-in admin user.
[1.8.1] Bump version
2017-06-20 14:27:05 +00:00
1.8.1 Release notes (2017-6-20)
Extract admin status from the refresh token (#1078) * Extract admin status from the refresh token Fixes #1063 * wire up rpc
2017-06-17 14:59:15 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
Do not throw when the Sync constructor isn’t there (#1086) * Do not throw when the Sync constructor isn’t there with unified packaging it’s there all the time now Closes #1084 Fixes #996 * Fix running the sync tests when Sync is disabled
2017-06-20 13:40:54 +00:00
* Accessing `Realm.Sync` when sync is not enabled will no longer throw, but return `undefined`.
Include property names in type error exceptions thrown by Realm.create (#1069) * Add and adopt `Value::is_binary` / `Value::to_binary` / `Value::from_binary`. These methods allow conversions between `BinaryData` and the equivalent JavaScript types without using `NativeAccessor`. Instead, `NativeAccessor` now itself delegates to these methods. * Have `NativeAccessor::value_for_property` and `RealmObjectClass::set_property` verify that values are valid for the property in question. If not, we throw an exception that includes the name and type of the property in question. `NativeAccessor` is changed to always hold a reference to a `Realm` and an `ObjectSchema` in order to make this validation possible. * Fix the Windows build. * Remove an unused, incorrect forward declaration of a template class named `Realm` that caused ambiguity with object store's `Realm` class. * Disambiguate between `realm::js::PropertyType` and `realm::PropertyType`. * Update CHANGELOG.md
2017-06-20 12:40:01 +00:00
* Better error messages when creating objects.
adding ts and package.json typings (#1076) * adding ts and package.json typings * remove DefinitelyTyped needed comments, we are hosting this ourselves * adding licensing comments * Added initial contribution support Thanks @akim95 * changing year * adding parameters * Expand on collection typings * update the windows pre-gyp script (#1072) * Extract admin status from the refresh token (#1078) * Extract admin status from the refresh token Fixes #1063 * wire up rpc * Make sure all callbacks enqueue on the Node.js event loop (#1079) Fixes #1077 * Use an uncached realm instance for _waitForDownload (#1083) Fixes #1061 * Add objectSchema method to Realm Object (#1055) * Add objectSchema property to Realm Object * fix * fixes * move typings under lib/ * changelog
2017-06-20 11:09:01 +00:00
* Added bundled TypeScript declarations of the Realm API.
[1.8.1] Bump version
2017-06-20 14:27:05 +00:00
* Added `objectSchema()` method on `Realm.Object` that returns the schema for the object.
Extract admin status from the refresh token (#1078) * Extract admin status from the refresh token Fixes #1063 * wire up rpc
2017-06-17 14:59:15 +00:00
### Bug fixes
* Fix `Realm.Sync.User.prototype.isAdmin` returning `false` for logged-in admin users.
[1.8.0] Bump version
2017-06-15 14:27:43 +00:00
1.8.0 Release notes (2017-6-15)
Support the new React Native C++ bridge (#1065) * Support the new React Native C++ bridge Fixes #1049 * address code review comments * handle the case when the websocket executor does not exist
2017-06-14 12:44:28 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
[1.8.0] Bump version
2017-06-15 14:27:43 +00:00
* Updated core and sync dependencies
* Unified packaging
Support the new React Native C++ bridge (#1065) * Support the new React Native C++ bridge Fixes #1049 * address code review comments * handle the case when the websocket executor does not exist
2017-06-14 12:44:28 +00:00
### Bug fixes
* Fix crash when used with the React Native C++ bridge
[1.8.0] Bump version
2017-06-15 14:27:43 +00:00
* Fix `Realm.open` and `Realm.asyncOpen` missing when in the React Native debugger
Support the new React Native C++ bridge (#1065) * Support the new React Native C++ bridge Fixes #1049 * address code review comments * handle the case when the websocket executor does not exist
2017-06-14 12:44:28 +00:00
[1.3.1] Bump version
2017-05-18 11:13:28 +00:00
1.3.1 Release notes (2017-5-18)
[1.3.0] Bump version
2017-05-11 12:34:52 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
Fix changelog
2017-05-18 11:03:21 +00:00
* Add Realm open async API support.
[1.3.0] Bump version
2017-05-11 12:34:52 +00:00
### Bug fixes
* None
1.3.0 Release notes (2017-5-11)
=============================================================
Use core 2.5.1 and sync 1.5.0 (#949) * Use core 2.5.1 and sync 1.5.0 * Add changelog entry
2017-03-29 11:41:17 +00:00
### Breaking changes
* Files written by Realm this version cannot be read by earlier versions of Realm.
Old files can still be opened and files open in read-only mode will not be modified.
Add a changelog entry
2017-05-05 11:53:20 +00:00
* The `setVerifyServersSslCertificate` method has been deleted
* The SyncConfig now gets two more optional parameters, `validate_ssl` and `ssl_trust_certificate_path`.
Use core 2.5.1 and sync 1.5.0 (#949) * Use core 2.5.1 and sync 1.5.0 * Add changelog entry
2017-03-29 11:41:17 +00:00
### Enhancements
Fix changelog
2017-05-18 11:03:21 +00:00
* None
Use core 2.5.1 and sync 1.5.0 (#949) * Use core 2.5.1 and sync 1.5.0 * Add changelog entry
2017-03-29 11:41:17 +00:00
### Bug fixes
* None
[1.2.0] Bump version
2017-03-28 12:49:58 +00:00
1.2.0 Release notes (2017-3-28)
Fix opening synced realm with an encryption key (#945)
2017-03-28 12:34:27 +00:00
=============================================================
### Breaking changes
* This version is not compatible with versions of the Realm Object Server lower than 1.3.0.
### Enhancements
* None.
### Bug fixes
* Fixed bug where opening synced realms with an encryption key would fail.
[1.1.1] Bump version
2017-03-09 13:35:30 +00:00
1.1.1 Release notes (2017-3-9)
Node.js Win32 support (#864) * Remove the windows install check * Node.js Win32 support * Bring back the `REALM_HAVE_CONFIG` definition * Download core for Windows when building * Implement cross-platform node platform.cpp with libuv * wip * Make jasmine run quicker https://github.com/jasmine/jasmine/issues/1204 * Wait for worker process to close in AsyncTests * Cross-platform paths in tests * Normalize path separator for forward slash on Windows * MSVC exception voodoo * cross-platform uv_cwd * fix linux build * make the prepublish script cross-platform * Disable encryption tests on windows * ignore vendor/realm-node * jenkinsfile work * Only run the prepublish script for publish and pack * Jenkinsfile work * Include gyp files in package * rewrite default_realm_file_directory() * fix React Native Android build * delete all realm artifacts in remove_realm_files_from_directory * bring back build environment variables * node-pre-gyp windows * Update CHANGELOG.md
2017-03-07 22:24:30 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
[1.1.0] Bump version
2017-03-09 10:53:00 +00:00
* Add support for Node.js on Windows (#863).
Nh/fixes 866 (#867)
2017-02-15 12:56:21 +00:00
### Bug fixes
* Fixed an error when installing Realm React Native module on Windows (#799).
### Credits
* Thanks to David Howell (@dbhowell) for adding a fix to Windows install (#849).
[1.0.2] Bump version
2017-02-07 12:01:16 +00:00
1.0.2 Release notes (2017-2-7)
Implement proactive access token refresh (#842) Closes #840
2017-02-03 15:40:13 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bug fixes
* Proactively refresh sync user tokens to avoid a reconnect delay (#840)
[1.0.1] Bump version
2017-02-02 14:50:17 +00:00
1.0.1 Release notes (2017-2-2)
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bug fixes
* Fix crash when the sync user token expires (#839)
[1.0.0] Bump version
2017-02-02 12:51:53 +00:00
1.0.0 Release notes (2017-2-2)
Add Permissions models and User Management Realm API (#824) * Add Permissions models and User Management Realm API * docs and changelog * fix bad merge * add test * fix jsdoc annotation * rename permissions to management schema
2017-01-31 21:56:09 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* Add the Management Realm accessor on the User class, and its schema (#779)
### Bug fixes
* None
[0.15.4] Bump version
2017-01-11 11:53:01 +00:00
0.15.4 Release notes (2017-1-11)
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bug fixes
* Always download Node binaries except on Windows, for unit testing (#789)
[0.15.3] Bump version
2017-01-10 15:21:11 +00:00
0.15.3 Release notes (2017-1-10)
=============================================================
### Breaking changes
* None
### Enhancements
* More specific error message when setting a property to a wrong type (#730)
### Bug fixes
* Fix chrome debugging on React Native 0.39 and up (#766)
[0.15.2] Bump version
2016-12-29 09:35:07 +00:00
0.15.2 Release notes (2016-12-29)
=============================================================
### Breaking changes
* None
### Enhancements
* More explicit handling of missing constructor (#742)
### Bugfixes
* Realm open on another thread (#473)
* symbol() variable not found (#761)
[0.15.1-rc] Bump version
2016-11-23 00:42:07 +00:00
0.15.1 Release notes (2016-11-22)
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bugfixes
* Fix compile error for collection notification in chrome debug mode
[0.15.0-rc] Bump version
2016-11-15 13:42:25 +00:00
0.15.0 Release notes (2016-11-15)
add empty changelog section
2016-08-15 18:13:28 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
[0.15.0] Bump version
2016-11-15 19:10:07 +00:00
* Node.js support
* Support for fine grained notifications on `List` and `Results` objects
[0.15.0-rc] Bump version
2016-11-15 13:42:25 +00:00
* Updated test and examples for react-natve v0.37.0
add empty changelog section
2016-08-15 18:13:28 +00:00
### Bugfixes
* None
[0.14.3-rc] Bump version
2016-08-08 17:32:17 +00:00
0.14.3 Release notes (2016-8-8)
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bugfixes
Nh/fixes 866 (#867)
2017-02-15 12:56:21 +00:00
* Support for react-native v0.31.0
[0.14.3-rc] Bump version
2016-08-08 17:32:17 +00:00
0.14.2 Release notes (2016-8-3)
rebase fixes
2016-08-04 17:11:53 +00:00
=============================================================
### Breaking changes
* Deprecate `Realm.Types`. Please specify the type name as lowercase string instead.
### Enhancements
* None
### Bugfixes
* None
[0.14.2] Bump version
2016-07-11 20:18:40 +00:00
0.14.2 Release notes (2016-7-11)
Add CHANGELOG item about rnpm 1.9.0+ support
2016-06-22 18:34:58 +00:00
=============================================================
### Breaking changes
* Please use `rnpm 1.9.0` or later to link your project. Older versions are no longer supported.
[0.14.2] Bump version
2016-07-11 20:18:40 +00:00
* ReactNative versions older than v0.14.0 are no longer supported
Add CHANGELOG item about rnpm 1.9.0+ support
2016-06-22 18:34:58 +00:00
### Enhancements
[0.14.2] Bump version
2016-07-11 20:18:40 +00:00
* Support for ReactNative versions v0.28.0+
Add support for debugging in Visual Studio Code Since Code runs in Node, rather than Chrome, we need to require the `sync-request` module. The global `__debug__` object was exposed by the vscode-react-native plugin v0.1.5 for us to be able to do that. Resolves #374
2016-04-28 23:08:38 +00:00
* Added support for debugging in Visual Studio Code.
Add CHANGELOG item about rnpm 1.9.0+ support
2016-06-22 18:34:58 +00:00
### Bugfixes
[0.14.2] Bump version
2016-08-04 00:56:48 +00:00
* None
Add CHANGELOG item about rnpm 1.9.0+ support
2016-06-22 18:34:58 +00:00
[0.14.0-rc] Bump version
2016-06-28 19:15:36 +00:00
0.14.1 Release notes (2016-6-28)
Fix for linker error when building for iOS 7 By default, React Native projects target a minimum of iOS 7, but our projects were set to iOS 8 because previously we used a dynamic framework. When building for an iOS 7 minimum target version, the linker would complain about thread local variables not working on iOS 7. So it was necessary to add even more checks (iOS >= 8 or OS X >= 10.7) before using native thread local variables rather than our shim. This also changes our projects to target iOS 7 so we can catch these issues quicker in the future.
2016-06-27 19:16:35 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bugfixes
* Fix linker error when building for minimum target version of iOS 7.
Disable "Strip Linked Product" on our static libs There seems to a bug inside the `strip` command (or its `ld64` library) that is being triggered by some users who get this message: `Assertion failed: (0 && "need to handle arm64 -r reloc")` It is reported that disabling this setting side-steps the issue, and we don't need any stripping done on the static library itself. Fixes #503
2016-06-28 19:12:56 +00:00
* Fix for failure in `strip` command when building an archive.
Fix for linker error when building for iOS 7 By default, React Native projects target a minimum of iOS 7, but our projects were set to iOS 8 because previously we used a dynamic framework. When building for an iOS 7 minimum target version, the linker would complain about thread local variables not working on iOS 7. So it was necessary to add even more checks (iOS >= 8 or OS X >= 10.7) before using native thread local variables rather than our shim. This also changes our projects to target iOS 7 so we can catch these issues quicker in the future.
2016-06-27 19:16:35 +00:00
[0.14.0] Bump version
2016-06-22 15:42:27 +00:00
0.14.0 Release notes (2016-6-22)
changlog
2016-05-19 21:10:20 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
Update CHANGELOG for 0.14.0 release
2016-06-17 00:52:57 +00:00
* Added `isValid()` method to `List` and `Results` to check for deleted or invalidated objects
Update docs and CHANGELOG with objectForPrimaryKey
2016-06-03 23:59:50 +00:00
* Added `objectForPrimaryKey(type, key)` method to `Realm`
changlog
2016-05-19 21:10:20 +00:00
Merge branch '0.13.x' * 0.13.x: [0.13.1] Bump version Fix crash and other errors with Results snapshots fix for negative timestamps
2016-05-24 19:38:32 +00:00
### Bugfixes
fix for setting properties to objects from other realms
2016-06-08 18:22:12 +00:00
* Fix for crash when setting object properties to objects from other Realms
Update CHANGELOG for 0.14.0 release
2016-06-17 00:52:57 +00:00
* Fix for exception sometimes thrown when reloading in Chrome debug mode
Merge branch '0.13.x' * 0.13.x: [0.13.1] Bump version Fix crash and other errors with Results snapshots fix for negative timestamps
2016-05-24 19:38:32 +00:00
[0.13.2] Bump version
2016-05-26 20:31:39 +00:00
0.13.2 Release notes (2016-5-26)
fix for upgrading optional date properties
2016-05-26 20:17:19 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* None
### Bugfixes
* Fix for crash when updating Realms with optional date properties to the new file format
[0.13.1] Bump version
2016-05-24 18:53:10 +00:00
0.13.1 Release notes (2016-5-24)
fix for negative timestamps
2016-05-24 15:23:21 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* None
changlog
2016-05-19 21:10:20 +00:00
### Bugfixes
CHANGELOG.md
2016-05-24 15:24:18 +00:00
* Fix for crash when inserting dates from before the epoch
Fix crash and other errors with Results snapshots When deleteAll() is called on a Realm, it calls clear() on all of its Tables, which seems to not update TableViews unless they are synced. The is_row_attached(row_ndx) method still returns true otherwise. A workaround is here until that is fixed. Fixes #434
2016-05-20 20:42:17 +00:00
* Fix for crash when using collection snapshot after realm.deleteAll()
changlog
2016-05-19 21:10:20 +00:00
[0.13.0] Bump version
2016-05-19 20:33:50 +00:00
0.13.0 Release notes (2016-5-19)
Update CHANGELOG.md
2016-05-16 20:56:59 +00:00
=============================================================
### Breaking changes
* With this release we have switched over to a new cross platform compatible date format.
This change will only require action from users who are using both the JS and Cocoa or Android
bindings simultaneously and accessing Realm files from both bindings. In these cases you need to
open the Realm file with the latest version of the iOS or Android bindings before accessing the
Realm from JS to prevent an unnecessary conversion.
### Enhancements
* None
### Bugfixes
* Date properties are now stored in a format compatible with the Realm Browser and other bindings.
Update CHANGELOG.md with the rest of 0.13.0 changes
2016-05-16 21:42:21 +00:00
* Fix for using `class MyObject extends Realm.Object` in a React Native project.
* Fix a memory leak caused by constructing a Realm instance of an already opened Realm.
* Fix for better supporting hot module reloading.
* Fix for some warnings when using `ListView` with React Native 0.25+
Update CHANGELOG with parser fix
2016-05-19 19:40:16 +00:00
* Fix for queries that use a keypath starting with "not".
Update CHANGELOG.md
2016-05-16 20:56:59 +00:00
[0.12.0] Bump version
2016-05-04 20:48:19 +00:00
0.12.0 Release notes (2016-5-4)
pr feedback, changelog
2016-04-12 15:13:29 +00:00
=============================================================
### Breaking changes
* None
### Enhancements
* Support for queries comparing optional properties to `null`
Update CHANGELOG.md
2016-04-27 00:14:15 +00:00
* `object.isValid()` has been added to enable checking if an object has been deleted
Update CHANGELOG with missing items
2016-05-03 01:38:43 +00:00
- **Note:** Custom object classes can extend `Realm.Object` to inherit this method
* Support opening a Realm as read-only with the `readOnly` configuration option
* Support for providing a custom migration function (please see the docs for details)
* Added `path`, `readOnly`, `schema`, and `schemaVersion` properties to `Realm` instances
* Optional and list properties are no longer required when creating objects
pr feedback, changelog
2016-04-12 15:13:29 +00:00
### Bugfixes
changelog
2016-04-19 23:09:10 +00:00
* When accessing an empty Results `undefined` is returned rather than throwing an exception
Update CHANGELOG with crash fix
2016-04-28 19:52:15 +00:00
* Accessing a deleted object throws a JS exception rather than crashing
* Accessing an invalidated Results snapshot throws a JS exception rather than crashing
changelog
2016-05-02 19:46:34 +00:00
* Fix for error message when specifying properties with invalid object types
Update CHANGELOG with missing items
2016-05-03 01:38:43 +00:00
* Fix memory leak when reloading an app in debug mode
changelog
2016-05-03 20:06:41 +00:00
* Setting non-persisted properties now works as expected
pr feedback, changelog
2016-04-12 15:13:29 +00:00
Update CHANGELOG with 0.11.1 fixes
2016-03-29 22:30:15 +00:00
0.11.1 Release notes (2016-3-29)
=============================================================
### Bugfixes
* Fix for using Android Studio to build app using Realm
* Fix for sharing Realm between JS and Objective-C/Swift
Update CHANGELOG for final 0.11.0 release
2016-03-24 19:14:14 +00:00
0.11.0 Release notes (2016-3-24)
changelog
2016-03-11 00:15:54 +00:00
=============================================================
Update CHANGELOG for final 0.11.0 release
2016-03-24 19:14:14 +00:00
### Breaking changes
* Realm for React Native is now packaged as a static library for iOS
- Remove the reference to `RealmJS.xcodeproj` from your Xcode project
(under the `Libraries` group)
- Make sure `rnpm` is installed and up-to-date: `npm install -g rnpm`
- Run `rnpm link realm` from your app's root directory
backfill changelog
2016-03-11 00:24:12 +00:00
changelog
2016-03-11 00:15:54 +00:00
### Enhancements
Update CHANGELOG for final 0.11.0 release
2016-03-24 19:14:14 +00:00
* Support for encrypted Realms
Make List and Results inherit from Collection This will allow for easier type checking, documentation, etc.
2016-03-09 07:47:08 +00:00
* List and Results now inherit from Realm.Collection
Update CHANGELOG for final 0.11.0 release
2016-03-24 19:14:14 +00:00
* List and Results is now iterable (e.g. supports `for...of` loops)
backfill changelog
2016-03-11 00:24:12 +00:00
* Add common Array methods to List and Results
* Accept constructor in create() and objects() methods
Update CHANGELOG for final 0.11.0 release
2016-03-24 19:14:14 +00:00
* Support relative paths when opening Realms
* Support case insensitive queries by adding `[c]` after operators
* Support for indexed `bool`, `string`, and `int` properties
* Added `Realm.schemaVersion` method, which supports unopened Realms
backfill changelog
2016-03-11 00:24:12 +00:00
changelog
2016-03-11 00:15:54 +00:00
### Bugfixes
changelog
2016-03-15 20:56:51 +00:00
* Fix for crash on Android when initializing the Realm module
Update changelog
2016-03-16 19:54:39 +00:00
* Fix for using Chrome debug mode from a device
Update CHANGELOG with splice method fix
2016-03-17 21:56:07 +00:00
* Fix for List splice method not accepting a single argument
backfill changelog
2016-03-11 00:24:12 +00:00
* Don't download or unpack core libraries unnecessarily
changelog
2016-03-11 00:15:54 +00:00
backfill changelog
2016-03-11 00:24:12 +00:00
0.10.0 Release notes (2016-2-22)
=============================================================
### Enhancements
Update changelog
2016-03-16 19:54:39 +00:00
* Initial Release