discourse/app/models/concerns/has_search_data.rb

# frozen_string_literal: true

module HasSearchData
  extend ActiveSupport::Concern

  included do
    _associated_record_name = self.name.sub('SearchData', '').underscore
    self.primary_key = "#{_associated_record_name}_id"
    belongs_to _associated_record_name.to_sym
    validates_presence_of :search_data
  end
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-02 18:17:27 -04:00			`# frozen_string_literal: true`

Fix: unlinked topic search model (#5044) 2017-08-15 11:46:57 -04:00			`module HasSearchData`
			`extend ActiveSupport::Concern`

			`included do`
Fix 'asscoiated' typo I know that Naming is CRITICAL and that Refactoring only NOT welcome. But since I spotted this (consistent) typo and the change does not affect any functionality -- I checked the presence of "asscoiated" in the code base, I guess the first rule trumps the second one. It also gave me a false pretext to bypass my reluctance to use Google forms and sign de CLA. Typos hurt the eye. 2018-06-26 12:32:13 -04:00			`_associated_record_name = self.name.sub('SearchData', '').underscore`
			`self.primary_key = "#{_associated_record_name}_id"`
			`belongs_to _associated_record_name.to_sym`
Fix: unlinked topic search model (#5044) 2017-08-15 11:46:57 -04:00			`validates_presence_of :search_data`
			`end`
			`end`