discourse/db/migrate/20230907225057_create_theme_settings_migrations.rb

# frozen_string_literal: true

class CreateThemeSettingsMigrations < ActiveRecord::Migration[7.0]
  def change
    create_table :theme_settings_migrations do |t|
      t.integer :theme_id, null: false
      t.integer :theme_field_id, null: false
      t.integer :version, null: false
      t.string :name, null: false, limit: 150
      t.json :diff, null: false
      t.datetime :created_at, null: false
    end

    add_index :theme_settings_migrations, %i[theme_id version], unique: true
    add_index :theme_settings_migrations, :theme_field_id, unique: true
  end
end
FEATURE: Theme settings migrations (#24071) This commit introduces a new feature that allows theme developers to manage the transformation of theme settings over time. Similar to Rails migrations, the theme settings migration system enables developers to write and execute migrations for theme settings, ensuring a smooth transition when changes are required in the format or structure of setting values. Example use cases for the theme settings migration system: 1. Renaming a theme setting. 2. Changing the data type of a theme setting (e.g., transforming a string setting containing comma-separated values into a proper list setting). 3. Altering the format of data stored in a theme setting. All of these use cases and more are now possible while preserving theme setting values for sites that have already modified their theme settings. Usage: 1. Create a top-level directory called `migrations` in your theme/component, and then within the `migrations` directory create another directory called `settings`. 2. Inside the `migrations/settings` directory, create a JavaScript file using the format `XXXX-some-name.js`, where `XXXX` is a unique 4-digit number, and `some-name` is a descriptor of your choice that describes the migration. 3. Within the JavaScript file, define and export (as the default) a function called `migrate`. This function will receive a `Map` object and must also return a `Map` object (it's acceptable to return the same `Map` object that the function received). 4. The `Map` object received by the `migrate` function will include settings that have been overridden or changed by site administrators. Settings that have never been changed from the default will not be included. 5. The keys and values contained in the `Map` object that the `migrate` function returns will replace all the currently changed settings of the theme. 6. Migrations are executed in numerical order based on the XXXX segment in the migration filenames. For instance, `0001-some-migration.js` will be executed before `0002-another-migration.js`. Here's a complete example migration script that renames a setting from `setting_with_old_name` to `setting_with_new_name`: ```js // File name: 0001-rename-setting.js export default function migrate(settings) { if (settings.has("setting_with_old_name")) { settings.set("setting_with_new_name", settings.get("setting_with_old_name")); } return settings; } ``` Internal topic: t/109980 2023-11-02 13:10:15 +08:00			`# frozen_string_literal: true`

			`class CreateThemeSettingsMigrations < ActiveRecord::Migration[7.0]`
			`def change`
			`create_table :theme_settings_migrations do \|t\|`
			`t.integer :theme_id, null: false`
			`t.integer :theme_field_id, null: false`
			`t.integer :version, null: false`
			`t.string :name, null: false, limit: 150`
			`t.json :diff, null: false`
			`t.datetime :created_at, null: false`
			`end`

			`add_index :theme_settings_migrations, %i[theme_id version], unique: true`
			`add_index :theme_settings_migrations, :theme_field_id, unique: true`
			`end`
			`end`