kallithea Files · rhodecode/templates/admin/notifications/notifications

Files @ fc63a1d93803

Branch filter:

Location: kallithea/rhodecode/templates/admin/notifications/notifications_data.html

fc63a1d93803 1.4 KiB text/html Show Annotation Show as Raw Download as Raw

Marcin Kuzminski

Switched order of actions when doing repo rescan.

doing invalidation after repository scan is not optimal.
In case of big repository we first create an instance then invalidate
cache that we don't actually need. Reversing this order prevents that


%if c.notifications:
<%
unread = lambda n:{False:'unread'}.get(n)
%>


<div class="notification-list  notification-table">
%for notification in c.notifications:
  <div id="notification_${notification.notification.notification_id}" class="container ${unread(notification.read)}">
    <div class="notification-header">
      <div class="gravatar">
          <img alt="gravatar" src="${h.gravatar_url(h.email_or_none(notification.notification.created_by_user.email),24)}"/>
      </div>
      <div class="desc ${unread(notification.read)}">
      <a href="${url('notification', notification_id=notification.notification.notification_id)}">${notification.notification.description}</a>
      </div>
      <div class="delete-notifications">
        <span id="${notification.notification.notification_id}" class="delete-notification delete_icon action"></span>
      </div>
      %if not notification.read:
      <div class="read-notifications">
        <span id="${notification.notification.notification_id}" class="read-notification accept_icon action"></span>
      </div>
      %endif
    </div>
    <div class="notification-subject">${h.literal(notification.notification.subject)}</div>
  </div>
%endfor
</div>

<div class="notification-paginator">
  <div class="pagination-wh pagination-left">
  ${c.notifications.pager('$link_previous ~2~ $link_next',**request.GET.mixed())}
  </div>
</div>

%else:
    <div class="table">${_('No notifications here yet')}</div>
%endif