Skip to content

After save details #578

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

Merged
merged 2 commits into from
Dec 13, 2018
Merged

Conversation

acinader
Copy link
Contributor

In my first attempt at upgrading to parse 3, I did it in such a way that our afterSave hooks were now blocking the response, so I looked into what was going on and figured it should be better documented.

Try to improve afterSave documentation to include:

  1. How to ensure that afterSave runs async if necessary
  2. That request.context is a feature and how to use it.

I also added a real-world code example that uses modern javascript.

1. How to ensure that afterSave runs async if necessary
2. That request.context is a feature and how to use it.

I also added a real world code example that uses modern javascript.
@acinader acinader requested a review from flovilmart December 12, 2018 22:00
@acinader
Copy link
Contributor Author

doh. I didn't notice #566 I'll take a look....

Copy link
Contributor

@flovilmart flovilmart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@acinader acinader merged commit 33c4597 into parse-community:gh-pages Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants