gitlab-org--gitlab-foss/lib/gitlab/slash_commands/issue_command.rb

module Gitlab
  module SlashCommands
    class IssueCommand < BaseCommand
      def self.available?(project)
        project.issues_enabled? && project.default_issues_tracker?
      end

      def collection
        IssuesFinder.new(current_user, project_id: project.id).execute
      end
    end
  end
end
Rename from service, and move to lib/gitlab 2016-11-16 12:28:38 -05:00			`module Gitlab`
Rename "Slash commands" to "Quick actions" Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27070 Deprecate "chat commands" in favor of "slash commands" We looked for things like: - `slash commmand` - `slash_command` - `slash-command` - `SlashCommand` 2017-05-31 01:50:53 -04:00			`module SlashCommands`
Rename from service, and move to lib/gitlab 2016-11-16 12:28:38 -05:00			`class IssueCommand < BaseCommand`
Refactor and test Slash commands This is the structure Kamil proposed, which leaves us with a bunch of smaller classes. This commits deletes outdated files and tests everything from the SlashCommandService and down (child classes and subcommands) 2016-11-15 15:50:27 -05:00			`def self.available?(project)`
First steps on refactoring Mattermost Slash commands Now, each subcommand has its own service, plus I've introduced presenters to be able to delegate the generation of the views. 2016-11-15 03:55:56 -05:00			`project.issues_enabled? && project.default_issues_tracker?`
issue and mergerequest slash command for mattermost This commit includes a couple of thing: - A chatops controller - Mattermost::CommandService - Mattermost::Commands::(IssueService\|MergeRequestService) The controller is the point where mattermost, and later slack will have to fire their payload to. This in turn will execute the CommandService. Thats where the authentication and authorization should happen. So far this is not yet implemented. This should happen in later commits. Per subcommand, in case of `/gitlab issue show 123` issue whould be the subcommand, there is a service to parse the data, and fetch the resource. The resource is passed back to the CommandService which structures the data. 2016-11-12 05:17:24 -05:00			`end`

			`def collection`
Add issue search slash command One of many requested in: gitlab-org/gitlab-ce#24768 2016-11-25 09:41:28 -05:00			`IssuesFinder.new(current_user, project_id: project.id).execute`
issue and mergerequest slash command for mattermost This commit includes a couple of thing: - A chatops controller - Mattermost::CommandService - Mattermost::Commands::(IssueService\|MergeRequestService) The controller is the point where mattermost, and later slack will have to fire their payload to. This in turn will execute the CommandService. Thats where the authentication and authorization should happen. So far this is not yet implemented. This should happen in later commits. Per subcommand, in case of `/gitlab issue show 123` issue whould be the subcommand, there is a service to parse the data, and fetch the resource. The resource is passed back to the CommandService which structures the data. 2016-11-12 05:17:24 -05:00			`end`
			`end`
			`end`
			`end`