mirror of
https://gh.wpcy.net/https://github.com/discourse/discourse.git
synced 2026-05-15 01:05:49 +08:00
3332e9f4c3
`.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.
37 lines
885 B
Ruby
37 lines
885 B
Ruby
# frozen_string_literal: true
|
|
|
|
class PostReplyKey < ActiveRecord::Base
|
|
belongs_to :post
|
|
belongs_to :user
|
|
|
|
before_validation { self.reply_key ||= self.class.generate_reply_key }
|
|
|
|
validates :post_id, presence: true
|
|
validates :user_id, presence: true
|
|
validates :reply_key, presence: true
|
|
|
|
def reply_key
|
|
super&.delete("-")
|
|
end
|
|
|
|
def self.generate_reply_key
|
|
SecureRandom.hex(16)
|
|
end
|
|
end
|
|
|
|
# == Schema Information
|
|
#
|
|
# Table name: post_reply_keys
|
|
#
|
|
# id :bigint not null, primary key
|
|
# reply_key :uuid not null
|
|
# created_at :datetime not null
|
|
# updated_at :datetime not null
|
|
# post_id :integer not null
|
|
# user_id :integer not null
|
|
#
|
|
# Indexes
|
|
#
|
|
# index_post_reply_keys_on_reply_key (reply_key) UNIQUE
|
|
# index_post_reply_keys_on_user_id_and_post_id (user_id,post_id) UNIQUE
|
|
#
|
