Files
simple-aircraft-manager-rails/app/mailers/reminder_mailer.rb
T
rickyandClaude Opus 5.5 d8cd462194 Configurable roles: Owner, Mechanic, Pilot, Viewer and custom roles
What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).

- Roles are installation-wide sets of permissions (31, grouped as flying,
  squawks and notes, maintenance records, imports and exports, the
  aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
  managed), Mechanic (shop maintenance: logbook, signing, components,
  inspections, ADs, squawks, reminders), Pilot (what pilots could do
  before) and Viewer (view only). Administrators can change all but
  Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
  remove or add. On the aircraft's Access page, anyone who manages people
  hands out roles, but only an Owner can give or take away Owner, nobody
  changes their own (except administrators), and an aircraft always
  keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
  changes something with none declared is refused (and raises in
  development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
  the DRS reminder also needs Manage ADs. The API follows the person's
  role; its owners_only error is now not_permitted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 17:43:38 -05:00

51 lines
2.3 KiB
Ruby

class ReminderMailer < ApplicationMailer
# Aircraft where the user's role includes the permission.
def self.aircraft_where(user, permission)
Aircraft.where(id: AircraftRole.with_permission(permission).where(user_id: user.id).select(:aircraft_id)).ordered
end
# [[aircraft, issues, new AD alerts], …] for the aircraft the user gets
# reminders for (their role's "gets reminders") that need attention.
def self.items_for(user)
aircraft_where(user, :receive_reminders)
.map { [ _1, _1.airworthiness.issues, _1.ad_alerts.pending.to_a ] }.reject { _2.empty? && _3.empty? }
end
def self.expiring_certificates_for(user) = user.certificates.expiring.to_a
def self.audit_due_for?(user) = user.admin? && AuditRun.due_soon?
# Aircraft they get reminders for and manage the ADs of, whose AD baseline
# needs a (new) DRS import: none yet, a year old, or a model never covered.
def self.drs_due_for(user)
aircraft_where(user, :receive_reminders)
.where(id: AircraftRole.with_permission(:manage_ads).where(user_id: user.id).select(:aircraft_id))
.select { DrsImport.renewal_due?(_1) || DrsImport.missing_models(_1).any? }
end
# The DRS reminder rides along with any other news; on its own it's sent
# on the first Monday of the month only, not every week.
def self.anything_for?(user, today: Date.current)
items_for(user).any? || expiring_certificates_for(user).any? || audit_due_for?(user) ||
(today.day <= 7 && drs_due_for(user).any?)
end
def weekly(user)
Time.use_zone(user.time_zone.presence || Time.zone_default) { weekly_in_zone(user) }
end
private
def weekly_in_zone(user)
@user = user
@items = self.class.items_for(user)
@certificates = self.class.expiring_certificates_for(user)
@audit_due = self.class.audit_due_for?(user) && AuditRun.next_due
@drs_due = self.class.drs_due_for(user)
overdue = @items.sum { |_, issues, _| issues.count { _1.severity.in?(%w[RED LIMITED]) } }
subject = overdue.positive? ? t(".subject_overdue", count: overdue) : t(".subject_due")
subject = t(@certificates.any? ? ".subject_certificate" : (@audit_due ? ".subject_audit" : ".subject_drs")) if @items.empty?
mail subject: [ subject, @items.map { _1.first.tail_number }.to_sentence.presence ].compact.join(": "), to: user.email_address
end
end