discourse/lib/reviewable/editable_fields.rb

# frozen_string_literal: true

class Reviewable < ActiveRecord::Base
  class EditableFields < Reviewable::Collection
    class Field < Item
      attr_reader :type

      def initialize(id, type)
        super(id)
        @type = type
      end

      def server_action
        id
      end
    end

    def add(id, type)
      @content << Field.new(id, type)
    end
  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-03 06:17:27 +08:00			`# frozen_string_literal: true`

FEATURE: New 'Reviewable' model to make reviewable items generic Includes support for flags, reviewable users and queued posts, with REST API backwards compatibility. Co-Authored-By: romanrizzi <romanalejandro@gmail.com> Co-Authored-By: jjaffeux <j.jaffeux@gmail.com> 2019-01-04 01:03:01 +08:00			`class Reviewable < ActiveRecord::Base`
			`class EditableFields < Reviewable::Collection`
			`class Field < Item`
			`attr_reader :type`

			`def initialize(id, type)`
			`super(id)`
			`@type = type`
			`end`
FIX: Don't mix up action labels between different reviewables (#23365) Currently, if the review queue has both a flagged post and a flagged chat message, one of the two will have some of the labels of their actions replaced by those of the other. In other words, the labels are getting mixed up. For example, a flagged chat message might show up with an action labelled "Delete post". This is happening because when using bundles, we are sending along the actions in a separate part of the response, so they can be shared by many reviewables. The bundles then index into this bag of actions by their ID, which is something generic describing the server action, e.g. "agree_and_delete". The problem here is the same action can have different labels depending on the type of reviewable. Now that the bag of actions contains multiple actions with the same ID, which one is chosen is arbitrary. I.e. it doesn't distinguish based on the type of the reviewable. This change adds an additional field to the actions, server_action, which now contains what used to be the ID. Meanwhile, the ID has been turned into a concatenation of the reviewable type and the server action, e.g. post-agree_and_delete. This still provides the upside of denormalizing the actions while allowing for different reviewable types to have different labels and descriptions. At first I thought I would prepend the reviewable type to the ID, but this doesn't work well because the ID is used on the server-side to determine which actions are possible, and these need to be shared between different reviewables. Hence the introduction of server_action, which now serves that purpose. I also thought about changing the way that the bundle indexes into the bag of actions, but this is happening through some EmberJS mechanism, so we don't own that code. 2023-09-06 10:57:30 +08:00
			`def server_action`
			`id`
			`end`
FEATURE: New 'Reviewable' model to make reviewable items generic Includes support for flags, reviewable users and queued posts, with REST API backwards compatibility. Co-Authored-By: romanrizzi <romanalejandro@gmail.com> Co-Authored-By: jjaffeux <j.jaffeux@gmail.com> 2019-01-04 01:03:01 +08:00			`end`

			`def add(id, type)`
			`@content << Field.new(id, type)`
			`end`
			`end`
			`end`