Skip to content

v2.2.0

Latest
Compare
Choose a tag to compare
@leemaguire leemaguire released this 22 Jul 17:27
· 3 commits to main since this release
01152ac

Fixed

  • Using the == operator in a type safe query for a nullable string property would return the incorrect result when algined storage was disabled.
  • Fix compilation issue when building with Bionic due to use of std::tuple (since 2.1.0).

Enhancements

  • Add ability to use managed<std::map<std::string, T>> in type safe queries when comparing a value for a key. e.g.
    realm.object<MyObject>().where([](auto& o) { return o.my_map["foo_key"] == "some value"; })
    Supported operators are ==, !=, >, <, >=, <= and contains(const std::string&).
  • Add managed<std::map<std::string, T>>::contains_key for conveniently checking if a managed map
    contains a given key. Use this method in the Type Safe Query API instead of managed<std::map<std::string, T>>::find.
  • Add realm::networking namespace which contains interfaces for providing your own custom network transport
    implementations. The following interfaces are exposed:
    • websocket_interface
    • websocket_observer
    • sync_socket_provider
    • sync_socket_provider::timer
    • http_transport_client
  • Add default_http_transport for built-in HTTP transport.
  • Add default_socket_provider a built-in class for providing the components necessary for transport via WebSocket.
  • A custom WebSocket & HTTP transport implementation can be used by passing
    the instance via realm::app::App::configuration.http_transport_client & realm::app::App::configuration.sync_socket_provider.
  • Network configuration for the built-in http transport must be supplied via it's constructor using the
    realm::networking::default_http_transport::configuration struct.
  • Network configuration for the built-in websocket provider must be supplied via it's constructor using the
    realm::networking::default_socket_provider::configuration struct.

Deprecations

  • Proxy and custom http headers should no longer be set via realm::app::App::configuration.

Compatibility

  • Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10.

Internals

  • Upgraded to Core v14.11.0