Add afterLogout trigger docs #684
Conversation
* commit 'e129790ed587819ecfcaed59fc7ff90ec6ffcfa1': (84 commits) Add `cascadeSave` option in ParseObject to JS docs (parse-community#664) Update apple sign in documentation (parse-community#662) Bump mixin-deep from 1.3.1 to 1.3.2 (parse-community#670) Update GraphQL docs with latest changes (parse-community#669) remove a bunch of parse cloud references (parse-community#654) docs: fixed examples for pipeline in aggregation (parse-community#661) Add beta notice to the GraphQL Guide (parse-community#659) iOS Documentation Revamp (parse-community#650) Fix doc for creating a subscription in javascript (parse-community#658) GraphQL Customisation (parse-community#652) added PhantAuth authData docs (parse-community#655) Fix typo in keys.md (parse-community#656) Fix typo in cloud-code.md (parse-community#657) add reference to afterFind, add more detail on predefined classes (parse-community#653) Add `keys` and `excludeKeys` options to REST docs (parse-community#649) document push type and priority keys for notifications (parse-community#639) Documentation for Sign In With Apple (parse-community#648) Documentation for isDataAvailable (parse-community#647) Remove line for 3.x (parse-community#646) Add documentation for query.withCount (parse-community#645) ...
|
Docs for parse-community/parse-server#6217 |
|
Next release will be 4.0.0. It’s going to be massive, trust me |
|
@TomWFox Thanks, just as reminder for us:
|
|
@mtrezza there is a merge conflict - I don't have time to resolve it now so if you can that would be great or I'll get to it in a day or so |
|
@TomWFox let me take a look at it... |
|
@TomWFox the merge conflict is the auto-generated |
|
Not sure, we did have this problem before, I seem to remember we just kept the version from the upstream master but I'm not certain. |
|
@TomWFox What I could do is to rebase and submit a new PR, to be on the safe side. I think I won't be able to push to this branch after rebase. What do you think? |
|
If I remember correctly we want to keep the upstream master bundle.js files since it gets generated. @acinader explained the process here #606 (comment) |
|
Thanks @dplewis, resolved by keeping upstream changes, ready to merge. And you were right, 3.10 was massive! 👏 |
|
Should we add it to the gitignore since it will be generated anyway? Sorry not too familiar with the bundle process. |
|
@dplewis gitignore makes sense to me, file is generated on every run. |
Todo before merging:
*Available only on parse-server cloud code starting 3.10.0*if necessary.