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

Add context to object save in JS SDK #730

Merged
merged 10 commits into from
Jul 27, 2020

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented Apr 18, 2020

Added description for new feature to expose Cloud Code trigger context in Parse.Object.save().


Don't merge until

* 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)
  ...
* commit 'cc489df4a3d8544a52148c079ecaee3d1762108d':
  Adding microsoft oauth doc (parse-community#698)
  Encrypting Current User and Local Storage (parse-community#695)
  Update live-query.md (parse-community#696)
  Update config.md (parse-community#689)
  Fix User Subclass Documentation (parse-community#690)
  remove info about parse.com compatibility (parse-community#686)
Copy link
Contributor

@TomWFox TomWFox left a comment

Choose a reason for hiding this comment

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

Looks good, one wee suggestion.

Also, I think it would be worth including this in the cloud code guide too. You could link to the content in the JS guide or vice versa but considering it’s a relatively small section I would just copy and paste it in.

_includes/js/objects.md Outdated Show resolved Hide resolved
Co-Authored-By: Tom Fox <13188249+TomWFox@users.noreply.github.com>
mtrezza added 2 commits April 18, 2020 22:48
- added headings per trigger group
- moved context of save triggers into own section
TomWFox
TomWFox previously approved these changes Apr 18, 2020
Copy link
Contributor

@TomWFox TomWFox left a comment

Choose a reason for hiding this comment

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

Barring any changes to the implementation, this looks fab.

I love when people organise all their PRs nicely & take care of the docs early in the process, it makes it sooo much easier for us!

@mtrezza
Copy link
Member Author

mtrezza commented Apr 18, 2020

The first thing I think of before starting a PR is "Which changes in the docs would make Tom happy?" 😌

@TomWFox
Copy link
Contributor

TomWFox commented Apr 18, 2020

❤️

I think I might actually make a bot that comments that on every PR to a Parse repo 😅😝

@mtrezza
Copy link
Member Author

mtrezza commented Apr 19, 2020

@TomWFox Do we have a guideline for adding the required minimum parse server version for a new feature to the docs?

I rarely see something like “Requires Parse Server v1.2”. Should that be added or do we expect users to find that out in the change log?

Sent with GitHawk

@TomWFox
Copy link
Contributor

TomWFox commented Apr 19, 2020

Good point, we don’t have a guideline for this but probably should.

When there is a clear section for a new feature in the docs I think it makes sense to add a note, like in some sections of the Cloud Code guide...
IMG_0901

I’ve been bitten by this when I was trying to use request context only to realise that it wasn’t included in the version I was running.

@mtrezza
Copy link
Member Author

mtrezza commented Apr 19, 2020

Yes, I also found some of these:

image

@mtrezza mtrezza closed this Apr 19, 2020
@mtrezza mtrezza reopened this Apr 19, 2020
@TomWFox TomWFox merged commit 7042a47 into parse-community:gh-pages Jul 27, 2020
@mtrezza
Copy link
Member Author

mtrezza commented Jul 27, 2020

Uh, I lost track of that one, thanks @TomWFox

@TomWFox
Copy link
Contributor

TomWFox commented Jul 27, 2020

No probs, me too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants