v0.15.1May 18, 2017
⚡️ Update for Rails 5.1
When sorting entries by
created_at, also sort by
iddescending. This is to ensure proper sorting of items for databases that do not store nanoseconds for timestamp columns.
- When trying to delete a Mailboxer object, a
NameErrormay be thrown due to a missing namespace
- 🚅 Rails 5 compatibility.
Mailboxer::Messageobject no longer requires to have a subject.
- Objects are now saved before mails are sent, you you can use them in the 🏗 mailer templates (to build URLs, for example).
- Errors are now stored in the parent message/notification instead of being stored in the sender receipt. That means you need handle mailboxer related ⬆️ controller and views differently, and study the upgrade case by case (propably by having a look at mailboxer's source code). As an example, if you were previously doing something like this in your controller:
@receipt = @actor.send_message(@recipients, params[:body], params[:subject]) if (@receipt.errors.blank?) @conversation = @receipt.conversation redirect_to conversation_path(@conversation) else render :action => :new end
you now need to do something like
@receipt = @actor.send_message(@recipients, params[:body], params[:subject]) @message = @receipt.message if (@message.errors.blank?) @conversation = @message.conversation redirect_to conversation_path(@conversation) else render :action => :new end
🏗 This might look more complicated at first but allows you to build more RESTful 🏗 resources since you can build forms on messages and/or conversations and directly show errors on them. Less specially handling is now required to propagate errors around models.
v0.13.0July 02, 2015
- check if messages are valid before trying to save them
- ⬆️ Upgrade to Rspec 3
- 🚅 Rails 4.2 support
v0.12.4September 08, 2014
v0.12.3August 31, 2014
v0.12.2August 16, 2014
v0.12.1June 16, 2014
v0.12.0June 05, 2014