discourse/migrations/lib/database/intermediate_db/user_associated_account.rb
Gerhard Schlager 89f26da39d
MT: Switch to nested module style across migrations/ (#38564)
Ruby's compact module syntax (`module
Migrations::Database::Schema::DSL`) breaks lexical constant lookup —
`Module.nesting` only includes the innermost constant, so every
cross-module reference must be fully qualified. In practice this means
writing `Migrations::Database::Schema::Helpers` even when you're already
inside `Migrations::Database::Schema`.

Nested module definitions restore the full nesting chain, which brings
several practical benefits:

- **Less verbose code**: references like `Schema::Helpers`,
`Database::IntermediateDB`, or `Converters::Base::ProgressStep` work
without repeating the full path from root
- **Easier to write new code**: contributors don't need to remember
which prefixes are required — if you're inside the namespace, short
names just work
- **Fewer aliasing workarounds**: removes the need for constants like
`MappingType = Migrations::Importer::MappingType` that existed solely to
shorten references
- **Standard Ruby style**: consistent with how most Ruby projects and
gems structure their namespaces

The diff is large but mechanical — no logic changes, just module
wrapping and shortening references that the nesting now resolves.
Generated code (intermediate_db models/enums) keeps fully qualified
references like `Migrations::Database.format_*` since it must work
regardless of the configured output namespace.

- Convert 138 lib files from compact to nested module definitions
- Remove now-redundant fully qualified prefixes and aliases
- Update model and enum writers to generate nested modules with correct
indentation
- Regenerate all intermediate_db models and enums
2026-03-19 18:15:19 +01:00

57 lines
1.6 KiB
Ruby

# frozen_string_literal: true
# This file is auto-generated from the IntermediateDB schema. To make changes,
# update the configuration files in "migrations/config/schema/" and then run
# `migrations/bin/cli schema generate` to regenerate this file.
module Migrations
module Database
module IntermediateDB
module UserAssociatedAccount
SQL = <<~SQL
INSERT INTO user_associated_accounts (
user_id,
provider_name,
created_at,
info,
last_used,
provider_uid
)
VALUES (
?, ?, ?, ?, ?, ?
)
SQL
private_constant :SQL
# Creates a new `user_associated_accounts` record in the IntermediateDB.
#
# @param user_id [Integer, String]
# @param provider_name [String]
# @param created_at [Time, nil]
# @param info [Object, nil]
# @param last_used [Time, nil]
# @param provider_uid [String]
#
# @return [void]
def self.create(
user_id:,
provider_name:,
created_at: nil,
info: nil,
last_used: nil,
provider_uid:
)
Migrations::Database::IntermediateDB.insert(
SQL,
user_id,
provider_name,
Migrations::Database.format_datetime(created_at),
Migrations::Database.to_json(info),
Migrations::Database.format_datetime(last_used),
provider_uid,
)
end
end
end
end
end