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

alias for destroy #1447

Open
3 tasks done
vince1995 opened this issue Feb 2, 2022 · 3 comments
Open
3 tasks done

alias for destroy #1447

vince1995 opened this issue Feb 2, 2022 · 3 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@vince1995
Copy link

vince1995 commented Feb 2, 2022

New Feature / Enhancement Checklist

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.

@parse-github-assistant
Copy link

parse-github-assistant bot commented Feb 2, 2022

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added the type:feature New feature or improvement of existing feature label Feb 6, 2022
@mtrezza
Copy link
Member

mtrezza commented Feb 6, 2022

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.

@vince1995
Copy link
Author

Using delete would be consistent with other SDKs. The names of the delete functions are also delete in Objective C, Java and Swift.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

2 participants