Read / Unread

This adds the concept of read/unread for notifications, and then the ability to toggle this through the user api.

I'm not sure though if the placement of tests in acceptance vs endpoint actually makes sense though.
IMO, it's a fine pattern.

On Wed, Nov 5, 2014 at 1:48 PM, Will Leinweber <notifications@github.com>
wrote:

> In lib/serializers/user_api/notification_serializer.rb:
>
> > @@ -6,6 +6,7 @@ class NotificationSerializer < Serializers::Base
> >          id:         n.id,
> >          created_at: time_format(n.created_at),
> >          title:      m.title,
> > +        read:       !!n.read_at,
>
> classic good or classic bad?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/heroku/telex/pull/23/files#r19908797>.
>