discourse/app/models/post_reply.rb
David Taylor 3332e9f4c3
DEV: Always pass --force to annotaterb and reorder annotations (#39977)
`.annotaterb.yml` has carried `classified_sort: true` since the project
switched from `annotate` to `annotaterb` (commit 0eab7daea4, July 2025),
but annotaterb's default behaviour is to compare the existing schema
block against what it would generate and skip the rewrite when the
column list matches — even when the *ordering* of those columns differs.
The result is that models which haven't had a schema change since the
config landed never get reordered, and `classified_sort` drift
accumulates indefinitely.

`--force` makes annotaterb always rewrite, so a single `bin/rake
annotate:clean` run brings every model into the canonical format and
keeps them there. Every schema block is now grouped primary-key →
regular columns → timestamps → foreign keys (alphabetical within each
group). Pure annotation comment change — no code modifications.

Also cleans up the rake task to avoid string interpolation for `system`
calls.
2026-05-13 14:12:48 +01:00

32 lines
802 B
Ruby

# frozen_string_literal: true
class PostReply < ActiveRecord::Base
belongs_to :post
belongs_to :reply, foreign_key: :reply_post_id, class_name: "Post"
validates :reply_post_id, uniqueness: { scope: :post_id }
validate :ensure_same_topic
private
def ensure_same_topic
if post.topic_id != reply.topic_id
self.errors.add(:base, I18n.t("activerecord.errors.models.post_reply.base.different_topic"))
end
end
end
# == Schema Information
#
# Table name: post_replies
#
# created_at :datetime not null
# updated_at :datetime not null
# post_id :integer
# reply_post_id :integer
#
# Indexes
#
# index_post_replies_on_post_id_and_reply_post_id (post_id,reply_post_id) UNIQUE
# index_post_replies_on_reply_post_id (reply_post_id)
#