rethinkdb / rethinkdb/docs

Add to .forEach documentation how to deal with a iteration that you don't wanna write

Open
#658 3 comments 0 reactions 1 assignee View on GitHub

@chipotle is already working on this.

Since Apr 13, 2015.

Dominant language
CSS
Stars
118
Forks
161
PR merge metrics
No merged PRs in 30d

Description

This can happen when you delete with returnChanges = true and expect old_val to have the old data but if two processes are concurrently deleting, one can end with old_val = nil, so the user should know that in this case he needs to return an empty array from forEach.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.