Project

no_notifier_needed

0.0
No commit activity in last 3 years
No release in over 3 years
no_notifier_neededblue-dog-archolite/no_notifier_neededHomepageDocumentationSource CodeBug TrackerWiki
A work in progress: Replace ActionMailer::Base class redundency. Temlating using haml or erb.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
128,313
Stars
0
Forks
1
Watchers
2
 Releases
Current version
2.4.5
Total releases
47
First release
2013-01-09
Latest release
2013-08-02
 Issues
Open Issues
1
Closed Issues
0
Total Issues
1
Issue Closure Rate
0%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
0
Merged Pull Requests
6
Pull Request Acceptance Rate
100%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2013-07-02
Reverse Dependencies
0

 Dependencies

Development

bundler
>= 1.2.3
debugger
>= 0
jeweler
~> 1.8.4
mail
>= 0
rails-pry
>= 0
rdoc
~> 3.12
script_finder
>= 0
shoulda
>= 0
simplecov
>= 0

Runtime

facets
~> 2.9.3
haml
>= 0
mandrill-api
>= 0
rails
>= 3.2.11
 Project Readme

no_notifier_needed¶ ↑

To Install¶ ↑

rails generate ‘no_notifier_needed:install’

Copies EmailProcessor, no_notifier_needed_initalizer, email_template, and email template migration into your rails application.

To send a template email: Notifier.send_now(email_template_name, any objects the template expects)

Example

Notifier.send_now("my_email", User.first, City.first, Topic) will translate to ->

EmailProcessor 	[{"which_email"=>"lead_intro", "user"=>105391, "city"=>1851, "topic"=>4121}] in Resque

and translated back to @user, @city, @topic

@user = User.find(105391)

@city = City.find(1851)

@topic = Topic.find(4121)

in the email template.

Use send_in to specify a delay before sending the email:

Notifier.send_in(5.days, "my_email", ...)

Use send_at to specify a time to send the email:

Notifier.send_at(3.days.from_now, "my_email", ...)

Contributing to no_notifier_needed¶ ↑

  • Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet.

  • Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it.

  • Fork the project.

  • Start a feature/bugfix branch.

  • Commit and push until you are happy with your contribution.

  • Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.

Copyright¶ ↑

Copyright © 2013 Robert R. Meyer. Just Kidding. MIT-LICENCE

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.