Permalink
Commits on May 18, 2017
  1. Bump version to 0.15.1

    jcoyne committed May 18, 2017
  2. Fix syntax error in migration

    jcoyne committed May 18, 2017
  3. Bump version to 0.15.0

    jcoyne committed May 18, 2017
  4. Merge pull request #461 from 3zcurdia/le-pg_search-support

    add pg_search support
    jcoyne committed on GitHub May 18, 2017
  5. Merge pull request #458 from avdept/master

    Added ability to query for not-deleted conversations
    jcoyne committed on GitHub May 18, 2017
  6. Merge pull request #451 from edwinwills/allow-notify-method-to-be-ren…

    …amed
    
    Allow the name of the `notify` method to be overridden
    jcoyne committed on GitHub May 18, 2017
  7. Merge pull request #440 from asselstine/master

    Added ability to specify custom mailers per mailable subclass
    jcoyne committed on GitHub May 18, 2017
Commits on May 17, 2017
  1. Merge pull request #463 from mailboxer/rails-5.1

    Add rails 5.1 support; Drop rails 4.2
    jcoyne committed on GitHub May 17, 2017
  2. Add rails 5.1 support; Drop rails 4.2

    jcoyne committed May 17, 2017
Commits on May 2, 2017
  1. add pg_search support

    3zcurdia committed May 2, 2017
Commits on Apr 13, 2017
Commits on Feb 27, 2017
  1. Merge pull request #453 from valer-cara/452-rollback-namespace-migration

    Fix rollback of namespace migration
    jcoyne committed on GitHub Feb 27, 2017
Commits on Feb 13, 2017
Commits on Feb 8, 2017
  1. Allow the name of the `notify` method to be overridden

    `notify` is a common method name used by other gems and in existing
    codebases - this change allows the notification method name to be
    overridden as part of the configuration for Mailboxer, to avoid method
    name clash with existing models that might already be using `.notify`
    edwinwills committed Feb 8, 2017
Commits on Aug 21, 2016
  1. Merge pull request #443 from t27duck/redo_413_to_fix_385

    Add missing namespaces so Mailboxer objects may be deleted
    jcoyne committed on GitHub Aug 21, 2016
  2. Merge pull request #442 from t27duck/use_hashes_for_wheres

    Use hashes and symbols for wheres where applicable
    jcoyne committed on GitHub Aug 21, 2016
  3. Use Rails conventions for ActiveRecord `where`s and `order`s

    When using `where` with a `joins`, you can reference the the join
    table as a key in a hash in `where`.
    
    Updated `Mailboxer::Receipt`, `Mailboxer::Notification`, and
    `Mailboxer::Conversation` to use this convention where possible.
    
    Also use a symbol and/or a hash for `order` where applicable.
    t27duck committed Aug 20, 2016
  4. Merge pull request #441 from t27duck/redo_361

    Use both created_at and id to order entires in proper order
    jcoyne committed on GitHub Aug 21, 2016
Commits on Aug 20, 2016
Commits on Aug 18, 2016
Commits on Jul 29, 2016
  1. Merge pull request #431 from deivid-rodriguez/bring_changelog_up_to_date

    Add a change log
    jcoyne committed on GitHub Jul 29, 2016
  2. Add a change log

    deivid-rodriguez committed Jul 29, 2016
Commits on Jul 28, 2016
  1. Bump version to 0.14.0

    jcoyne committed Jul 28, 2016
  2. Merge pull request #426 from t27duck/remove_rails_version_checks

    Remove defunct Rails version checks
    jcoyne committed on GitHub Jul 28, 2016
  3. Merge pull request #429 from deivid-rodriguez/more_improvements

    More improvements
    jcoyne committed on GitHub Jul 28, 2016
  4. Save objects in a more straight way

    It's simpler to just save the parent and let the children be autosaved
    (and autovalidated) since this is how Rails works out of the box. We
    just need to make sure the receipts are properly tied to the parent
    notification. We get that, again, by using Rails standard constructs
    like `association#build` instead of the ad-hoc `build_receipt` method.
    
    The previous behavior caused issues like getting duplicated errors in
    the notification object, because of the fact that everytime a receipt
    was saved, the parent notification would be saved too and validations
    would be (re)run.
    deivid-rodriguez committed Jul 26, 2016
  5. Follow up b6ffa85

    Since that commit, notifications no longer require a subject, so we'll
    never get duplicate validation errors and we don't need to clean those
    up.
    deivid-rodriguez committed Jul 26, 2016
  6. Add a regression test

    The `autosave` flag in the notifications's `belongs_to` is currently
    necessary but removing it woudn't make the tests fail. This test catches
    it.
    deivid-rodriguez committed Jul 26, 2016
Commits on Jul 26, 2016
Commits on Jul 25, 2016
  1. Merge pull request #428 from deivid-rodriguez/more_flexible_conversat…

    …ions
    
    More flexible conversations
    jcoyne committed on GitHub Jul 25, 2016
  2. Don't hardcode model / table name unless necessary

    Added a regression test because I was not sure removing the class name
    from the `belongs_to` would work. It does.
    deivid-rodriguez committed Jul 25, 2016
  3. Fix Rails 5 deprecation

    deivid-rodriguez committed Jul 25, 2016