discourse/lib/freedom_patches/safe_migrations.rb

# frozen_string_literal: true

# We do not run this in production cause it is intrusive and has
# potential to break stuff, it also breaks under concurrent use
# which rake:multisite_migrate uses
#
# The protection is only needed in Dev and Test
if ENV["RAILS_ENV"] != "production"
  require_dependency "migration/safe_migrate"
  Migration::SafeMigrate.patch_active_record!
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-03 08:17:27 +10:00			`# frozen_string_literal: true`

Revert "We have had errors reported due to migrations breaking and are reverting" This reverts commit 8b46f14744d4bab9339d075825914d86da6bd5eb. It corrects the reason for the revert: We rely on SafeMigrate existing cause we call it from migrations, Zeitwerk will autoload it. Instead of previous pattern we explicitly bypass all the hacks in production mode. We need to disable SafeMigrate cause it is not thread safe. A thread safe implementation is possible but not worth the effort, we catch the issues in dev and test. 2020-04-14 11:21:31 +10:00			`# We do not run this in production cause it is intrusive and has`
			`# potential to break stuff, it also breaks under concurrent use`
			`# which rake:multisite_migrate uses`
			`#`
			`# The protection is only needed in Dev and Test`
			`if ENV["RAILS_ENV"] != "production"`
			`require_dependency "migration/safe_migrate"`
			`Migration::SafeMigrate.patch_active_record!`
			`end`