Skip to content

COUCHDB-1755 notifications should take templates#56

Merged
asfgit merged 2 commits into
apache:masterfrom
deathbearbrown:1755-notifications-should-take-templates
May 15, 2013
Merged

COUCHDB-1755 notifications should take templates#56
asfgit merged 2 commits into
apache:masterfrom
deathbearbrown:1755-notifications-should-take-templates

Conversation

@deathbearbrown
Copy link
Copy Markdown
Member

Added the option to pass a template for custom notifications as well as data. Data is serialized so it can be accessed in the custom template.

@garrensmith
Copy link
Copy Markdown
Member

Thanks @deathbearbrown I've meged this into master. Could you close this pull request as I cant.

@asfgit asfgit merged commit c38ea8a into apache:master May 15, 2013
kocolosk added a commit that referenced this pull request Jun 29, 2013
Optimize db update notifications

BugzID: 13575
BugzID: 13600
nickva added a commit to cloudant/couchdb that referenced this pull request Apr 21, 2017
lag-linaro pushed a commit to lag-linaro/couchdb that referenced this pull request Oct 25, 2018
Always-on recursive application of all rebar commands causes too many
issues. Recursive application is required for:
1. dealing with dependencies: get-deps, update-deps, and compile of deps
   right after get-deps or update-deps
2. projects with a riak-like apps/ project structure and dev process

The vast majority of projects are not structured like riak. Therefore,
moving forward it's best to (by default) restrict recursive behavior to
dealing with deps. This commit does that and also adds command line and
rebar.config options for controlling or configuring recursion. Also, we
introduce two meta commands: prepare-deps (equivalent to rebar -r
get-deps compile) and refresh-deps (equivalent to rebar -r update-deps
compile). riak-like projects can extend the list of recursive commands
(to include 'eunit' and 'compile') by adding
{recursive_cmds, [eunit, compile]} to rebar.config.
jaydoane pushed a commit that referenced this pull request Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants