Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for custom object ids #1087

Closed
martinpfannemueller opened this issue Apr 9, 2021 · 2 comments
Closed

Support for custom object ids #1087

martinpfannemueller opened this issue Apr 9, 2021 · 2 comments
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@martinpfannemueller
Copy link
Contributor

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 Android SDK. I already tried to implement this by simply creating POST requests instead of a PUT in case allowCustomObjectId is true and an objectId is provided (see https://github.com/martinpfannemueller/Parse-SDK-Android). However, as I do not have the complete overview of the SDK, this currently does not really work yet.

Maybe there is somebody with more experience in developing the Android SDK who can provide this relatively simple feature more easily. In case I make progress, I will reference this issue in a possible pull request.

@cbaker6
Copy link

cbaker6 commented Apr 10, 2021

Though I haven’t used the Android SDK, I can tell from the code that the Android, IOS, and JS SDKs are designed the same. Because of this, the objectId in Android is probably never added to the encoded data sent to the parse server. I recommend looking at the JS PR I posted in response to your question I’m the iOS repo for guidance with fixing this here.

@mtrezza mtrezza added bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:improvement labels Oct 7, 2021
@azlekov
Copy link
Contributor

azlekov commented Nov 30, 2021

This was released with 2.1.0

@azlekov azlekov closed this as completed Nov 30, 2021
@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:improvement labels Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

4 participants