Skip to content

Realm

12 results found

  1. 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
    How important is this to you?
  2. Native Codable Support for BSON Document

    Supporting the codable protocol would clear out a lot of pain points in the swift sdk. I understand realm objects are classes not structs but implementing some kind of native conversion to Realm Objects would massively widen the set of use cases. Converting BSON docs from Remote access and GraphQL Queries to Realm objects is messy and lack any documentation. Having some kind of codable support would allow search functions and advanced MongoDB queries on a database with millions of objects without worrying about the sync infrastructure. It might not seem pertinent if you consider utility apps but if we…

    3 votes
    How important is this to you?
  3. Add the ability to manually set the internal name used by Realm for a class

    There is "RealmClass" annotation in android SDK.
    It can be used to set an internal name for some class: @RealmClass( "someName").
    It would be great to have this ability in swift SDK.
    It is not possible to set internal name for a class in swift SDK now.

    3 votes
    How important is this to you?
  4. Vapor (Swift Backend) Support

    Provide a native implementation of Realm for swift backend popular server-side Vapor.
    This will allow developers to apply the same technology Realm Swift for mobile apps and backend web application

    3 votes
    How important is this to you?
  5. Sync Linked Objects Automatically

    Please Sync Linked Objects automatically with the parent object. The jump in use cases and compatibility would be exponential.

    2 votes
    How important is this to you?
  6. 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
    How important is this to you?
  7. Apple Combine Integration

    Just like current support for RxSwift.

    2 votes
    How important is this to you?
  8. Decimal128

    It would be very convenient if Decimal128 had options for string formatting - it could then for example, more easily be used for currency. Similar to how a Double can be formatted

    As is, Swift Doubles have this feature:

     let myDouble = 1999.95
     let currencyFormatted = myDouble.formatted(.currency(code: "USD"))
     print(currencyFormatted)
    

    and the output is

     $1,999.95
    

    My suggest is to add a formatted feature to Decimal128

        let d = Decimal128(1999.95)
        let s = d.formatted(.currency(code: "USD"))
    
    1 vote
    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?
  9. Enable calling a nested Atlas function from Swift SDK

    Atlas app services allows organizing atlas functions into folders within a project, and you can call these nested functions from within other atlas functions. See this tip in your documentation for a quick explanation of this behavior: https://www.mongodb.com/docs/atlas/app-services/functions/#write-the-function-source-code

    That said, it is not currently possible to call a nested atlas function from the Swift SDK (you can only call top-level functions from the Swift SDK). This means that all publicly accessible functions must be located in the top-level of my functions directory of my project, which makes my files very unorganized and hard to find the function I'm looking for.

    1 vote
    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?
  10. Custom Init Documentation

    It would be great to have some documentation regarding how to go about custom initializing Realm objects in Swift. Most of the old docs which discussed the need/requirement for convenience init's has been removed. Also, most of the Git posts and replies date back to 2014/2015. So some clear guidance about using custom inits. (oh, and totally unrelated but some docs showing how to implement protocol's and codable Realm objects would be snappy! A LOT of folks ask about it on SO)

    1 vote
    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?
  11. 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
    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?
  12. 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
    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?
  • Don't see your idea?

Realm

Categories

Feedback and Knowledge Base