Realm
96 results found
-
13 votes
-
Single unified GeoJSON type
Generating a schema and consuming GeoJSON data in Realm is painful. Since GeoJSON has multiple 'types', Realm forces us to store a serialized string version of our GeoJSON, or to abstract our data out so that all GeoJSON objects follow the same generalized schema, which breaks some of the conveniences of GeoJSON.
Realm should allow for a GeoJSON type OR allow the schema to be dynamic (such as supporting ORs in the schema language itself).
3 votesSupport for geospatial data is ongoing - see the following documents for more information:
https://www.mongodb.com/docs/atlas/app-services/schemas/types/#geospatial-data
https://www.mongodb.com/docs/realm/sdk/node/model-data/data-types/geospatial/ (this for Node.js - see the other SDKs under "Data Types")
-
Collection indexes should be a part of exported Realm App config
As far as I understand, the only way to configure indexes is Realm UI, and those index settings are not exported along with other app configuration files. I think indexes are important part of the application and should be a part of exported configuration.
1 vote -
syncfusion.com support
Work with the Syncfusion.com Blazor UI components.
1 vote -
collection.watch support on React Native
Although in the documentation as working, this doesn't work (https://github.com/realm/realm-js/issues/3494) I pretty much built everything on Realm expecting this to work as documented.
It should be noted in the docs that this doesn't actually work. If there is a workaround available would be great to know about it, haven't been able to get it to work yet.1 vote -
react-native V8 compatibility
As there is still no compatibility with Hermes, use of react-native-v8 (https://github.com/Kudo/react-native-v8) may be a good alternative. Considering that there is already an implementation for node.js, this could be a viable path.
Realm performs well even on older devices, but in the general context of the project it is important to have a more performance JS engine for rendering. In some cases this can be a negative factor in adopting Realm in a project.Initial discussion here: https://github.com/realm/realm-js/issues/2875
9 votes -
Query Realm using MongoDB syntax
Now that Realm and MongoDB are so close, it would be nice to be able to use MongoDB-style queries on Realm as well. It seems to me that an object-based query language makes much more sense than a string-based one nowadays.
1 vote -
Query pagination
We are limited to one query without an offset. Support for pagination is important.
7 votes -
Customer feedback on Cocoapods
"I was looking for the pre-built version of the iOS SDK to download and install directly and that took me a bit to find. We don’t use Cocoapods, but the documentation really only describes using Cocoapods. Anyway I was able to find it on github recently, but I hadn’t thought to look there before. That might be a helpful addition to the docs for anyone installing it directly - I had to dig around quite a bit for it and wasn’t sure where to look."
1 vote -
Simple Way to Log Out a User From All Browser Tabs
Developers will often want to logout/login a user automatically from all the open tabs/windows.
Let's say you are developing a Single Page Application using
realm-webJS SDK.A user journey of the app will look like this: A user logs in with
app.logIn(credentials), and opens multiple tabs/windows on the browser. Then the user clicks the "Log out" button inside one of the tabs, and switches to another tab. The app UI remains the same, but http requests will fail.Although you might think it's a problem that each developer should tackle with, please consider to provide a native solution…
1 vote -
Realm Google Authentication Providers callback redirect
Hello, I am having problems with authentication via Google Authentication Providers.
The system prevents me from saving the backlink as:
chrome-extension://feomclaleplfhikikgnedghpnhozzzhb/index.htmlThrows an error: redirect URI must contain scheme of http or https
"chrome-extension://" is the standard URI scheme.Please add the ability to add a schema backlink for the chrome extension.
I cannot use other Google Authentication Providers because, if you build the application in the ElectronJS + Chrome-Extention configuration, ElectronJS does not support any authentication protocols. The only way out is to log in using the back link.
Regards, Alexander
1 vote -
Realm.open() method creating realm when not exists, should be made optional
Realm.open() method used in Middle Tier to fetch data would not find the realm and is waiting for data sync to happen from the device. This method can create a new realm if it does not exist which is not applicable in the context of the Middle Tier apps. Requesting an update to have this default realm creation functionality to be made optional based on a supplied optional parameter.
2 votes -
Documentation for Test (Jest)
There seems to be no documentation how to write good tests for realm at this moment.
10 votes -
Google Auth consent screen
Trying to use google authentication i have followed the documentation and the login flow works but because the redirect is mongodb.com url the google consent screen shows logging into mongodb which for the end user is going to be a redflag because that is not what they are signing in to.
11 votes -
nativescript support
Currently only react-native and node are supported.
Having tried to get the 'getting started' tutorials running I have come against a bit of a brick wall. Namely that dependencies are a nightmare.
Adding nativescript support would help to open realm to other web technologies including vue and angular.
6 votes -
Support Apple Watch (Sync)
Currently there is no support for sync on Apple Watch and no guidance on how to sync data between the apple watch and MongoDb Realm.
Previously the lack of websockets was listed as a reason for not supporting sync, but since watchOS 6.2 URLSessionWebSocketTask seems to provide the needed WebSocket.
Currently it is not clear how to build a watch app and sync data to the mobile app or to MongoDb Realm.
46 votes -
Integrate Gridfs in the realm sdk
Enable the use of gridfs with stitch apps in android.
4 votes -
Provide utility function to allow easier reading and usage of ObjectIds
Provide a utility that allows easier parsing of ObjectIds when they're returned to the client. As it stands, ObjectIds are returned as UInt8Arrays and cannot be readily used in the BSON.ObjectId constructor. Being able to retrieve specific items by ObjectId is necessary and the only way to do this dynamically (without knowing the hex string beforehand) is to retrieve the items and then use the returned id; however, as it stands, using the returned id is obfuscated and impractical.
I am now having to use the following workaround:
const toHexString = (bytes) =>
bytes.reduce((str, byte) => str + byte.toString(16).padStart(2, "0"),…2 votes -
Support for Vue / Nuxt
Support for Vue / Nuxt
10 votes -
Supporting backward compatibility
The requirement is backward compatibility. Let's say i have 3 apps from same family(i.e same app groups). These three apps access the same realm db using app group id.
For example - apps like gdrive, g docs and g sheet. All these app access/use the same db.
Similarly the app can use realm db and share the db with the app groups' apps.
as of now, If we update the main app's DB, we will have to set the new scheme version. if we set this, other apps will get crashed.
Note : Any changes in main app will need…
2 votes
- Don't see your idea?