mirror of
https://github.com/we-promise/sure.git
synced 2026-09-05 06:41:08 +00:00
Brandon
686205c0ff
* feat(bills): schema and domain core for the bills subsystem First of three chunks carved out of #3083. This one carries the schema and the domain layer: no bills pages, no calendar feed, no assistant tools. Nothing here is reachable from the UI yet, so it changes no user-visible behavior on its own. Schema, in a single migration with a full down: - recurrence_rules, recurring_occurrences, recurring_allocations, recurring_price_changes and recurring_match_rejections - bill columns on recurring_transactions (bill_type, payment_url, autopay, notes, anchor and end conditions, weekend adjustment, dedup scope) - the four data backfills, in their original order Domain layer: - Schedule, the pure date PORO every cadence resolves through, and FrequencyPreset for the labels - OccurrenceGenerator, Matcher, Allocator, PriceChangeDetector, Classifier, DeclaredBill, HistoryBackfiller and PaycheckPlanner - Pipeline, tying detection to generation, plus the nightly job and rake task Existing detection code changed in three places, each a bug this schema exposes: - Cleaner used a flat two-month staleness threshold, which silently retired every quarterly and annual series - SubscriptionAuditGenerator used a flat 45-day overdue threshold, meaningless at both ends of the frequency range - CashFlowWarningGenerator read one projected entry per series, which only equalled the monthly amount because every series was monthly; weekly bills were under-counted fourfold in its 30-day projection The JSON API travels with the model rather than the UI, because the status enum widens here. The API accepts only active and inactive on write; suggested, paused and ended are lifecycle states owned by detection, so the documented enum stays truthful. Uniqueness keys gain dedup_scope alongside amount, never instead of it: a series that is not price-forked carries a blank scope, so amount is what keeps two different prices apart. Suite 7,550 runs, 0 failures. Rubocop and brakeman clean. Eager loading verified, and the migration reverses and re-applies. Includes the first review round: orphan repair matches income and refuses coincidental twins, session imports persist occurrence mappings across chunks, semimonthly anchors canonicalize, classifier keywords match whole words, and the down refuses rather than failing when price-forked rows exist. * Address second review round Bound the cross-currency default allocation by the entry leftover and the occurrence remainder, matching the same-currency path. Let keyword stems carry a suffix again after the word-boundary fix silenced them. Skip an incoherent recurrence rule row instead of rolling back the whole import. Check rollback collisions per restored index so a refusal cannot land after the bills tables are dropped. Replay the closed_at test through a real second import. Preload the orphan repair associations and move the allocator errors to locale keys. * Match index NULL semantics in the rollback collision checks GROUP BY treats NULLs as equal but the restored unique indexes do not: account_id is nullable and indexed, so two accountless rows can never collide under any of them. Excluding NULL accounts keeps the guard from refusing a rollback PostgreSQL can perform. Verified live both ways: accountless duplicates roll back, a real collision still refuses. * Address maintainer review Scope the payable debt-destination subquery to the row and its family instead of scanning every account in the installation. Batch the cash flow generator remaining-amount sums into one grouped query, matching the two sibling sites. Enforce both window bounds in the after_count branch so a future-anchored plan cannot leak past the requested end date. Skip the explicit regeneration when the day column change will fire the model callback anyway. Add the missing locale entry for the allocation currency validation.
42 lines
1.5 KiB
Ruby
42 lines
1.5 KiB
Ruby
# One payment (or part of one) applied to one occurrence. Several allocations
|
|
# sum toward a single obligation -- that is the whole partial-payment model --
|
|
# and one entry may be split across several occurrences, each allocation
|
|
# carrying its own amount.
|
|
#
|
|
# entry_id is nullable by design: a payment recorded by hand (cash, or a bank
|
|
# feed that has not caught up) is a real payment with no entry. If an entry is
|
|
# later deleted, the FK nullifies rather than cascades, so the payment record
|
|
# and its amount survive.
|
|
class RecurringAllocation < ApplicationRecord
|
|
include Monetizable
|
|
|
|
belongs_to :recurring_occurrence
|
|
belongs_to :entry, optional: true
|
|
|
|
monetize :allocated_amount
|
|
|
|
enum :state, { suggested: "suggested", confirmed: "confirmed" }, prefix: :allocation
|
|
enum :source, { auto_matched: "auto_matched", user_confirmed: "user_confirmed",
|
|
user_created: "user_created" }, prefix: :from
|
|
|
|
validates :allocated_amount, presence: true, numericality: { greater_than: 0 }
|
|
validates :currency, presence: true
|
|
validate :currency_matches_occurrence
|
|
|
|
scope :confirmed, -> { where(state: :confirmed) }
|
|
scope :suggested, -> { where(state: :suggested) }
|
|
|
|
before_validation :default_paid_on
|
|
|
|
private
|
|
def currency_matches_occurrence
|
|
return if recurring_occurrence.nil? || currency == recurring_occurrence.currency
|
|
|
|
errors.add(:currency, :must_match_occurrence)
|
|
end
|
|
|
|
def default_paid_on
|
|
self.paid_on ||= entry&.date || Date.current
|
|
end
|
|
end
|