Kræn Hansen
Kræn Hansen
## Goals It would be great if the errors thrown would align on properties exposed and values used. This would enable sharing code which catches and handles errors regardless of...
The typescript declaration for `User` takes two generic types allow users to instantiate an app which returns users that expose type guarantees for the "Realm Functions" and "Custom data" they...
We've seen users experience the following error, when importing our package on outdated versions of Node.js: ``` undefined symbol: napi_add_finalizer ``` While we declare our supported engines in our `package.json`,...
### Problem Users want the simples way possible to query their data, but the current `useObject` and `useQuery` APIs take the `type` as an argument, which could be simplified further....
A [PR](https://github.com/realm/realm-js/pull/6405#issuecomment-1910200147) upgrading Realm Core, unveiled that passing a base URL without the `http` or `https` prefix, when creating an `App` instance would cause a crash 💥 We should either...
### Problem Some users want to access data from multiple Atlas clusters in a single app, meaning they'd want to access multiple `App` contexts from a single React component tree....
### Problem We have other teams at our organisation and potentially external users experiencing crashes, that would benefit from consuming the SDK via debug prebuilds. ### Solution This is supported...
Since we're only using `isEqual` from `lodash` we should avoid requiring in the entire library as it'll be difficult for end-users to shake off. Instead we could depend on the...
When using the babel plugin, it could be beneficial to see the schema in the Metro terminal. We could add support for this by reading a `DEBUG_REALM_SCHEMAS` env variable: ```...
We're currently only exposing the error message and `code`, while other properties are available on the native object.