You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I think it your suggested terminology makes sense. We could add delete as an alias and eventually deprecate destroy in the future. Not sure how widespread that change would be in terms of other Parse SDKs and / or related methods that contain the word destroy if there are any.
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: