Open
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
When I want to delete a Parse.Object
, I often try to call delete
instead of destroy
. Also, the cloud trigger is afterDelete
and not afterDestroy
, which is very confusing (for me).
Feature / Enhancement Description
Just an alias that delete
does the same as destroy
.
Example Use Case
See above
Alternatives / Workarounds
Maybe overwrite the Parse constructor in the index file.
3rd Party References
No 3rd party references.