Skip to content

Create 0001-after-find.md #2

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

Merged
flovilmart merged 1 commit into from
Oct 26, 2016
Merged

Create 0001-after-find.md #2

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
28 changes: 28 additions & 0 deletions proposals/0001-after-find.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Feature name

* Proposal: 0001-after-find
* Authors: [Jonas DB](https://github.com/jonas-db)
* Review Manager: TBD
* Status: **Awaiting review**

## Introduction
## Motivation

Assume that we want to know the amount of views of a blog post, so everytime a blog post is fetched with a GET request, the amount of views should be updated.

## Proposed solution

Introducing an afterFind cloud code function. This is similar to the existing triggers and provides a uniform way to have triggers for GET/POST/DELETE requests.

## Detailed design

Extending the cloud code with an afterFind function

## Alternatives considered

If i'm correct, there are two ways to solve this problem:

create a cloud function, which you call instead of querying a collection
after the fetch request, save the object again with the counter increased

While the first one is acceptable, the second is not. Although, I think that cloud code is meant for custom code, not for normal query requests. To remain consistent with the other cloud code, I propose the suggestion of afterFind.