90 results found

1. Allow (optional) read-only access to Realm objects after deletion

   Using Realm with reactive extensions, 3rd party libraries like DynamicData, and UI binding allows one to create beautifully dynamic, responsive apps with very few lines of clean code. This works fantastically for us in all scenarios except for when an item is deleted.

   As we all know, currently any attempt to access an item's properties after deletion throws an exception. This throws a huge spanner in the works for various reactive operations and UI bindings, which may (for implementation detail purposes of object equality checks, UI redraws queued in the event loop queue, or a bunch of other possibilities) still briefly try to read the properties of an object after deletion. Even sometimes just to remove it from an internal cache somewhere along the reactive processing chain when processing the deletion itself.

   As a result we have to constantly walk on eggshells in our code, put in lots of additional checks and filters and ugly hacks like flagging objects as deleted but not actually deleting them, or copying Realm object properties to keep them available, etc., just to try to avoid random app crashes that otherwise occur (since you can't catch these exceptions in any meaningful way when they occur in the middle of a reactive processing pipeline on the UI thread). And to date we have been far from totally successful.

   All this code ugliness and app brittleness could be avoided if Realm object properties could still be read after detaching. It could be opt-in, either on a per-object basis (e.g. there could be an overridable 'AllowDetachedRead' property or similar) or at the Realm level as part of config.

   Another way to offer this would be an optional 'AutoFreezeOnDetach' feature that automatically freezes the object in place when it is removed from the Realm. I tried doing this using existing functionality by calling FreezeInPlace() when the object becomes invalid, but that threw a native exception deep within the bowels of Realm. Not entirely surprised since by that point the object has already been deleted.

   So, can we have an option like this please? It would make life so much simpler and cleaner.

   Using Realm with reactive extensions, 3rd party libraries like DynamicData, and UI binding allows one to create beautifully dynamic, responsive apps with very few lines of clean code. This works fantastically for us in all scenarios except for when an item is deleted.

   As we all know, currently any attempt to access an item's properties after deletion throws an exception. This throws a huge spanner in the works for various reactive operations and UI bindings, which may (for implementation detail purposes of object equality checks, UI redraws queued in the event loop queue, or a bunch of other possibilities)… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Auto-Deinit Observers

   Would be really nice if auto-observers de-init automatically when tied to an optional object so if the object object is removed from memory (the user goes to a new view) the whole thing doesn't crash. :O

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm Swift SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. syncfusion.com support

   Work with the Syncfusion.com Blazor UI components.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm Swift SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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-web JS 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 in realm-web, if you think it's a common usecase for modern internet users.

   JFYI, one of the solutions would be listening to changes of LocalStorage by window.addEventListener("storage"), and it looks relatively simple to achieve:https://medium.com/front-end-weekly/multi-tab-logout-in-react-redux-4715f071c7fa

   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-web JS 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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm JS SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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.html

   Throws 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Support for MongoDB Transactions within SDKs

    Is it possible to support MongoDB Transactions within the SDKs?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close