Support for custom object ids

[martinpfannemueller]

Using the allowCustomObjectId option of parse-server, it is possible to provide custom object ids on the client side. It seems to me, that there is no support for this yet in the iOS SDK. I know that there is the new Swift SDK with support for this (https://github.com/parse-community/Parse-Swift/pull/100 and https://github.com/parse-community/Parse-Swift/pull/101). Is it planned to add this to this legacy iOS SDK as well? Or is this repository rather archived and there will be no new features anymore? Unfortunately I am still using the local datastore, so I am not able to migrate.

Thanks!

[TomWFox]

It's not planned to add said feature to the iOS SDK in that no one is currently working on it to my knowledge. There is currently very little feature development on this SDK but we do welcome contributions for this or anything else.

Currently the Swift SDK is seeing much more new feature development, thanks to @cbaker6. But at this time we have no intention of archiving the iOS SDK as it still plays an important role.

[cbaker6]

If you plan on implementing custom objectIds, I recommend looking at https://github.com/parse-community/Parse-SDK-JS/pull/1309. The same goes for many of the other missing features as the design of JS SDK is similar to this one.

I will say that the iOS SDK is written well and if some developers in the community decided to dedicate some time, it can be brought to feature parity with the JS and Swift SDKs. It won’t be easy though...

Using a local datastore for ParseSwift is possible, you just need to implement core data counterparts (if your datastore uses “structs” instead of classes, no need for counterparts) for your ParseObjects and store, fetch, and convert them on your own. An improvement to what I mentioned is discussed here: https://community.parseplatform.org/t/syncing-a-local-store/1455

[cbaker6]

@TomWFox a note about Parse-Swift and archiving the iOS SDK just in case this comes up in the future... Parse-Swift is based on using struct's to create ParseObjects and is Pure Swift which is why it can be built on Linux and Android. If I remember correctly, objective-c doesn't have the notion of struct's and uses classes only. Because of this, I'm confident you can't use Parse-Swift in Objective-C (but I've never tried. Even if someone did get it working, threading around reference types will cause issues). In summary, this means that if Parse wants to keep compatibility with Objective-C, it will need to keep the iOS SDK.

Swift programmers have the luxury of using either SDK, but my guess is for Swift apps, Parse-Swift would yield faster builds and a smaller app footprint.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide