discourse/app/models/child_theme.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

36 lines
997 B
Ruby

# frozen_string_literal: true
class ChildTheme < ActiveRecord::Base
belongs_to :parent_theme, class_name: "Theme"
belongs_to :child_theme, class_name: "Theme"
validate :child_validations
private
def child_validations
if Theme.where(
"(component IS true AND id = :parent) OR (component IS false AND id = :child)",
parent: parent_theme_id,
child: child_theme_id,
).exists?
errors.add(:base, I18n.t("themes.errors.no_multilevels_components"))
end
end
end
# == Schema Information
#
# Table name: child_themes
#
# id :integer not null, primary key
# created_at :datetime not null
# updated_at :datetime not null
# child_theme_id :integer
# parent_theme_id :integer
#
# Indexes
#
# index_child_themes_on_child_theme_id_and_parent_theme_id (child_theme_id,parent_theme_id) UNIQUE
# index_child_themes_on_parent_theme_id_and_child_theme_id (parent_theme_id,child_theme_id) UNIQUE
#