Skip to content

[proposal] Updating documentation about afterFind callbacks #7186

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.

Sign up for GitHub

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

Open
tony13tv wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[proposal] Updating documentation about afterFind callbacks #7186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/concepts/ORM/Lifecyclecallbacks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,14 @@ Lifecycle callbacks are functions that are called before or after certain model

Sails exposes a handful of lifecycle callbacks by default:

##### Lifecycle callbacks on `.find()`

- afterFind: fn(populatedRecords, proceed)

##### Lifecycle callbacks on `.findOne()`

- afterFindOne: fn(thePopulatedRecord, proceed)

##### Lifecycle callbacks on `.create()`

The `afterCreate` lifecycle callback will only be run on queries that have the `fetch` meta flag set to `true`. For more information on using the `meta` flags, see [Waterline Queries](https://sailsjs.com/documentation/reference/waterline-orm/queries/meta).
Expand Down