-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
alias for destroy
#1447
Labels
type:feature
New feature or improvement of existing feature
Comments
Thanks for opening this issue!
|
I think it your suggested terminology makes sense. We could add |
Using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
New Feature / Enhancement Checklist
Current Limitation
When I want to delete a
Parse.Object
, I often try to calldelete
instead ofdestroy
. Also, the cloud trigger isafterDelete
and notafterDestroy
, which is very confusing (for me).Feature / Enhancement Description
Just an alias that
delete
does the same asdestroy
.Example Use Case
See above
Alternatives / Workarounds
Maybe overwrite the Parse constructor in the index file.
3rd Party References
No 3rd party references.
The text was updated successfully, but these errors were encountered: