Skip to content

Conversation

NicksonYap
Copy link
Contributor

No description provided.

@NicksonYap
Copy link
Contributor Author

@flovilmart
Copy link
Contributor

@NicksonYap thanks for the PR. Does it really fit into the performance section?

@NicksonYap
Copy link
Contributor Author

@flovilmart you're welcome.

I'm not certain
I think it doesn't but I suppose it can be considered as Client-side caching?
Don't know what name to call this behaviour
To be honest I don't know what's the use of replacing server-side data with client-side data
Since calling find() or get() the object will trigger an API call anyways

@flovilmart
Copy link
Contributor

This isn’t caching. This feature is simply about discarding any changed keys from the client. The use of replacing server side data, is basically the core feature of parse, which is saving and updating objects

@TomWFox
Copy link
Contributor

TomWFox commented Mar 17, 2019

I wonder whether this would make sense in the data section.

Also could we get code samples for the other client SDKs as well?

@mtrezza
Copy link
Member

mtrezza commented Jul 1, 2024

I'l go ahead and merge this; could be helpful; fixed husky along the way...

@NicksonYap
Copy link
Contributor Author

Okie, I haven't been in the project for so long i don't recall what this is, all the best!

@mtrezza mtrezza changed the title Add JS doc for '.revert()' docs: Add JS doc for '.revert()' Jul 1, 2024
@mtrezza mtrezza changed the title docs: Add JS doc for '.revert()' docs: Add JS doc for Parse.Object.revert() Jul 1, 2024
@mtrezza mtrezza merged commit 254bb8d into parse-community:gh-pages Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants