rubocop-committee 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 85d35285a988e66ac1d5976d7ac3bf7ac7f207015d1fcd352eed7b8bdac60625
+  data.tar.gz: 6c2d9fa4b9d4d28bcbb596446e750a4befd6f0674301d1f03a1f5a604a5679b7
+SHA512:
+  metadata.gz: 2af73171d6c98048f001c48be91ebcf2a7c92c1dce94c1af6fb07cb91e1ace600f52d6787c3792dd12929a93e934fa1ac22f3e2db8c91831d21f1e9f65706436
+  data.tar.gz: 2fcb0125bdece926274d5b9cfab219497126bf3dbc599c386daa8ed3e02069c3a73f710c2de2d0efc98c2d24c213005b822de4c36c54a5181c9ec402a0fe96dc

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,32 @@
+require:
+  - rubocop/cop/internal_affairs
+  - rubocop-performance
+  - rubocop-rake
+  - rubocop-rspec
+
+AllCops:
+  NewCops: enable
+  TargetRubyVersion: 2.6
+  SuggestExtensions: false
+
+Layout/LineLength:
+  Enabled: false
+
+Metrics:
+  Enabled: false
+
+Naming/FileName:
+  Exclude:
+    - lib/rubocop-committee.rb
+
+Style/Documentation:
+  Enabled: false
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes
+
+RSpec/ExampleLength:
+  Enabled: false

data/.yamllint.yml

@@ -0,0 +1,9 @@
+extends: default
+
+rules:
+  comments:
+    min-spaces-from-content: 1
+  document-start: disable
+  line-length: disable
+  truthy:
+    check-keys: false

data/.yardopts

@@ -0,0 +1,2 @@
+--markup markdown
+--hide-void-return

data/CHANGELOG.md

@@ -0,0 +1,9 @@
+## Unreleased
+
+## 0.1.0 - 2022-12-29
+
+- Initial release ([@ydah])
+
+<!-- Contributors -->
+
+[@ydah]: https://github.com/ydah

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at 13041216+ydah@users.noreply.github.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+
+[homepage]: https://www.contributor-covenant.org

data/Gemfile

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gemspec
+
+gem 'bump', require: false
+gem "rake"
+gem "rspec"
+gem "rubocop-performance"
+gem "rubocop-rake"
+gem "rubocop-rspec"
+gem "yard"

data/MIT-LICENSE.md

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Yudai Takada
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,86 @@
+# RuboCop Committee
+
+![GitHub top language](https://img.shields.io/github/languages/top/ydah/rubocop-committee?color=39ff14) [![Gem Version](https://badge.fury.io/rb/rubocop-committee.svg)](https://badge.fury.io/rb/rubocop-committee) [![Ruby Style Guide](https://img.shields.io/badge/code_style-rubocop-brightgreen.svg)](https://github.com/rubocop/rubocop) [![CI](https://github.com/ydah/rubocop-committee/actions/workflows/ci.yml/badge.svg)](https://github.com/ydah/rubocop-committee/actions/workflows/ci.yml) [![Maintainability](https://api.codeclimate.com/v1/badges/a1b121696e9d1b425406/maintainability)](https://codeclimate.com/github/ydah/rubocop-committee/maintainability)
+
+Committee-specific analysis for your projects, as an extension to
+[RuboCop](https://github.com/rubocop/rubocop).
+
+## Installation
+
+Just install the `rubocop-committee` gem
+
+```bash
+gem install rubocop-committee
+```
+
+or if you use bundler put this in your `Gemfile`
+
+```
+gem 'rubocop-committee', require: false
+```
+
+## Usage
+
+You need to tell RuboCop to load the Committee extension. There are two
+ways to do this:
+
+### RuboCop configuration file
+
+Put this into your `.rubocop.yml`.
+
+```yaml
+require: rubocop-committee
+```
+
+Alternatively, use the following array notation when specifying multiple extensions.
+
+```yaml
+require:
+  - rubocop-other-extension
+  - rubocop-committee
+```
+
+Now you can run `rubocop` and it will automatically load the RuboCop Committee
+cops together with the standard cops.
+
+### Command line
+
+```bash
+rubocop --require rubocop-committee
+```
+
+### Rake task
+
+```ruby
+RuboCop::RakeTask.new do |task|
+  task.requires << 'rubocop-committee'
+end
+```
+
+## Documentation
+
+You can read more about RuboCop Committee in its official manual.
+
+## The Cops
+
+All cops are located under
+[`lib/rubocop/cop/committee`](lib/rubocop/cop/committee), and contain
+examples/documentation.
+
+In your `.rubocop.yml`, you may treat the Committee cops just like any other
+cop. For example:
+
+```yaml
+Committee/FilePath:
+  Exclude:
+    - spec/my_poorly_named_spec_file.rb
+```
+
+## Contributing
+
+Checkout the [contribution guidelines](.github/CONTRIBUTING.md).
+
+## License
+
+`rubocop-committee` is MIT licensed. [See the accompanying file](MIT-LICENSE.md) for
+the full text.

data/Rakefile

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+Dir["tasks/**/*.rake"].each { |t| load t }
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/config/default.yml

@@ -0,0 +1,19 @@
+---
+inherit_mode:
+  merge:
+    - Exclude
+
+Committee:
+  Enabled: true
+
+Committee/UnspecifiedExpectedStatus:
+  Description: |
+    Check if the status code is specified as an argument to the method of the Committee
+    where the expected response status code is required.
+  Enabled: pending
+  VersionAdded: '0.1'
+
+Committee/RedundantResponseStatusAssertions:
+  Description: Check for validation of redundant response HTTP status codes.
+  Enabled: pending
+  VersionAdded: '0.1'

data/docs/modules/ROOT/nav.adoc

@@ -0,0 +1,6 @@
+* xref:index.adoc[Home]
+* xref:installation.adoc[Installation]
+* xref:usage.adoc[Usage]
+* xref:cops.adoc[Cops]
+* Cops Documentation
+** xref:cops_committee.adoc[Committee]

data/docs/modules/ROOT/pages/cops.adoc

@@ -0,0 +1,8 @@
+// START_COP_LIST
+
+=== Department xref:cops_committee.adoc[Committee]
+
+* xref:cops_committee.adoc#committeeredundantresponsestatusassertions[Committee/RedundantResponseStatusAssertions]
+* xref:cops_committee.adoc#committeeunspecifiedexpectedstatus[Committee/UnspecifiedExpectedStatus]
+
+// END_COP_LIST

data/docs/modules/ROOT/pages/cops_committee.adoc

@@ -0,0 +1,66 @@
+= Committee
+
+== Committee/RedundantResponseStatusAssertions
+
+|===
+| Enabled by default | Safe | Supports autocorrection | Version Added | Version Changed
+
+| Pending
+| Yes
+| Yes
+| 0.1
+| -
+|===
+
+Check for validation of redundant response HTTP status codes.
+
+=== Examples
+
+[source,ruby]
+----
+# bad
+it 'something' do
+  subject
+  expect(response).to have_http_status 400
+  assert_schema_conform(400)
+end
+
+# good
+it 'something' do
+  subject
+  assert_schema_conform(400)
+end
+----
+
+== Committee/UnspecifiedExpectedStatus
+
+|===
+| Enabled by default | Safe | Supports autocorrection | Version Added | Version Changed
+
+| Pending
+| Yes
+| Yes
+| 0.1
+| -
+|===
+
+Check if the status code is specified as an argument to the method of the Committee
+where the expected response status code is required.
+
+=== Examples
+
+[source,ruby]
+----
+# bad
+it 'something' do
+  subject
+  expect(response).to have_http_status 400
+  assert_schema_conform
+end
+
+# good
+it 'something' do
+  subject
+  assert_schema_conform(400)
+end
+----

data/docs/modules/ROOT/pages/index.adoc

@@ -0,0 +1,15 @@
+= RuboCop Committee
+
+Committee-specific analysis for your projects, as an extension to
+https://github.com/rubocop/rubocop[RuboCop].
+
+RuboCop Committee follows the https://docs.rubocop.org/rubocop/versioning.html[RuboCop versioning guide].
+In a nutshell, between major versions new cops are introduced in a special `pending` status.
+That means that they won’t be run unless explicitly told otherwise.
+RuboCop will warn on start that certain cops are neither explicitly enabled and disabled.
+On a major version release, all `pending` cops are enabled.
+
+== Project Goals
+
+* Enforce the style of the test code to be best practice when using committee
+* Simplify the process of adopting new Committee functionality

data/docs/modules/ROOT/pages/installation.adoc

@@ -0,0 +1,15 @@
+= Installation
+
+Just install the `rubocop-committee` gem
+
+[source,bash]
+----
+gem install rubocop-committee
+----
+
+or if you use bundler put this in your `Gemfile`
+
+[source,ruby]
+----
+gem 'rubocop-committee'
+----

data/docs/modules/ROOT/pages/usage.adoc

@@ -0,0 +1,37 @@
+= Usage
+
+You need to tell RuboCop to load the RuboCop Committee extension.
+There are some ways to do this:
+
+== RuboCop configuration file
+
+Put this into your `.rubocop.yml`:
+
+----
+require: rubocop-committee
+----
+
+or, if you are using several extensions:
+
+----
+require:
+  - rubocop-committee
+  - rubocop-rspec
+----
+
+Now you can run `rubocop` and it will automatically load the RuboCop Committee
+cops together with the standard cops.
+
+[source,bash]
+----
+$ rubocop --require rubocop-committee
+----
+
+== Rake task
+
+[source,ruby]
+----
+RuboCop::RakeTask.new do |task|
+  task.requires << 'rubocop-committee'
+end
+----

data/docs/modules/antora.yml

@@ -0,0 +1,5 @@
+name: rubocop-committee
+title: RuboCop Committee
+version: "0.1.0"
+nav:
+  - modules/ROOT/nav.adoc

data/lib/rubocop/committee/inject.rb

@@ -0,0 +1,19 @@
+# frozen_string_literal: true
+
+require "rubocop"
+require "rubocop-rspec"
+
+module RuboCop
+  module Committee
+    module Inject
+      def self.defaults!
+        path = CONFIG_DEFAULT.to_s
+        hash = ::RuboCop::ConfigLoader.send(:load_yaml_configuration, path)
+        config = ::RuboCop::Config.new(hash, path).tap(&:make_excludes_absolute)
+        puts "configuration from #{path}" if ::RuboCop::ConfigLoader.debug?
+        config = ::RuboCop::ConfigLoader.merge_with_default(config, path)
+        ::RuboCop::ConfigLoader.instance_variable_set(:@default_configuration, config)
+      end
+    end
+  end
+end

data/lib/rubocop/committee/version.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+module Rubocop
+  module Committee
+    VERSION = "0.1.0"
+  end
+end

data/lib/rubocop/cop/committee/redundant_response_status_assertions.rb

@@ -0,0 +1,52 @@
+# frozen_string_literal: true
+
+module RuboCop
+  module Cop
+    module Committee
+      # Check for validation of redundant response HTTP status codes.
+      #
+      # @example
+      #   # bad
+      #   it 'something' do
+      #     subject
+      #     expect(response).to have_http_status 400
+      #     assert_schema_conform(400)
+      #   end
+      #
+      #   # good
+      #   it 'something' do
+      #     subject
+      #     assert_schema_conform(400)
+      #   end
+      #
+      class RedundantResponseStatusAssertions < Base
+        include RangeHelp
+        extend AutoCorrector
+
+        MSG = "Remove redundant HTTP response status code validation."
+        RESTRICT_ON_SEND = %i[assert_schema_conform assert_response_schema_confirm].freeze
+
+        # @!method have_http_status(node)
+        def_node_search :have_http_status, <<~PATTERN
+          $(send nil? :have_http_status (:int _))
+        PATTERN
+
+        def on_send(node)
+          return if node.first_argument.nil?
+
+          have_http_status(node.parent) do |http_node|
+            return autocorrect(node, http_node.parent.loc.expression)
+          end
+        end
+
+        private
+
+        def autocorrect(_node, bad_range)
+          add_offense(bad_range) do |corrector|
+            corrector.remove(range_by_whole_lines(bad_range, include_final_newline: true))
+          end
+        end
+      end
+    end
+  end
+end

data/lib/rubocop/cop/committee/unspecified_expected_status.rb

@@ -0,0 +1,55 @@
+# frozen_string_literal: true
+
+module RuboCop
+  module Cop
+    module Committee
+      # Check if the status code is specified as an argument to the method of the Committee
+      # where the expected response status code is required.
+      #
+      # @example
+      #   # bad
+      #   it 'something' do
+      #     subject
+      #     expect(response).to have_http_status 400
+      #     assert_schema_conform
+      #   end
+      #
+      #   # good
+      #   it 'something' do
+      #     subject
+      #     assert_schema_conform(400)
+      #   end
+      #
+      class UnspecifiedExpectedStatus < Base
+        include RangeHelp
+        extend AutoCorrector
+
+        MSG = "Specify the HTTP status code of the expected response as an argument."
+        RESTRICT_ON_SEND = %i[assert_schema_conform assert_response_schema_confirm].freeze
+
+        # @!method have_http_status(node)
+        def_node_search :have_http_status, <<~PATTERN
+          (send nil? :have_http_status (:int $_))
+        PATTERN
+
+        def on_send(node)
+          return if node.arguments?
+
+          have_http_status(node.parent) do |status|
+            return autocorrect(node, status)
+          end
+
+          add_offense(node)
+        end
+
+        private
+
+        def autocorrect(node, status)
+          add_offense(node) do |corrector|
+            corrector.insert_after(node, "(#{status})")
+          end
+        end
+      end
+    end
+  end
+end

data/lib/rubocop-committee.rb

@@ -0,0 +1,18 @@
+# frozen_string_literal: true
+
+require_relative "rubocop/committee/inject"
+require_relative "rubocop/committee/version"
+
+require_relative "rubocop/cop/committee/redundant_response_status_assertions"
+require_relative "rubocop/cop/committee/unspecified_expected_status"
+
+module RuboCop
+  module Committee
+    PROJECT_ROOT = ::Pathname.new(__dir__).parent.expand_path.freeze
+    CONFIG_DEFAULT = PROJECT_ROOT.join("config", "default.yml").freeze
+    CONFIG = ::YAML.safe_load(CONFIG_DEFAULT.read).freeze
+    private_constant(:CONFIG_DEFAULT, :PROJECT_ROOT)
+  end
+end
+
+RuboCop::Committee::Inject.defaults!

data/tasks/cops_documentation.rake

@@ -0,0 +1,48 @@
+# frozen_string_literal: true
+
+require "rubocop"
+require "rubocop-committee"
+require "rubocop/cops_documentation_generator"
+require "yard"
+
+YARD::Rake::YardocTask.new(:yard_for_generate_documentation) do |task|
+  task.files = ["lib/rubocop/cop/**/*.rb"]
+  task.options = ["--no-output"]
+end
+
+desc "Generate docs of all cops departments"
+task generate_cops_documentation: :yard_for_generate_documentation do
+  generator = CopsDocumentationGenerator.new(
+    departments: %w[Committee]
+  )
+  generator.call
+end
+
+desc "Syntax check for the documentation comments"
+task documentation_syntax_check: :yard_for_generate_documentation do
+  require "parser/ruby25"
+
+  ok = true
+  YARD::Registry.load!
+  cops = RuboCop::Cop::Registry.global
+  cops.each do |cop|
+    examples = YARD::Registry.all(:class).find do |code_object|
+      next unless RuboCop::Cop::Badge.for(code_object.to_s) == cop.badge
+
+      break code_object.tags("example")
+    end
+
+    examples.to_a.each do |example|
+      buffer = Parser::Source::Buffer.new("<code>", 1)
+      buffer.source = example.text
+      parser = Parser::Ruby25.new(RuboCop::AST::Builder.new)
+      parser.diagnostics.all_errors_are_fatal = true
+      parser.parse(buffer)
+    rescue Parser::SyntaxError => e
+      path = example.object.file
+      puts "#{path}: Syntax Error in an example. #{e}"
+      ok = false
+    end
+  end
+  abort unless ok
+end

data/tasks/cut_release.rake

@@ -0,0 +1,57 @@
+# frozen_string_literal: true
+
+require "bump"
+
+namespace :cut_release do
+  def update_file(path)
+    content = File.read(path)
+    File.write(path, yield(content))
+  end
+
+  %w[major minor patch pre].each do |release_type|
+    desc "Cut a new #{release_type} release and update documents."
+    task release_type do
+      run(release_type)
+    end
+  end
+
+  def version_sans_patch(version)
+    version.split(".").take(2).join(".")
+  end
+
+  # Replace `<<next>>` (and variations) with version being cut.
+  def update_cop_versions(version)
+    update_file("config/default.yml") do |default|
+      default.gsub(/['"]?<<\s*next\s*>>['"]?/i,
+                   "'#{version_sans_patch(version)}'")
+    end
+    RuboCop::ConfigLoader.default_configuration = nil # invalidate loaded conf
+  end
+
+  def update_docs(version)
+    update_file("docs/antora.yml") do |antora_metadata|
+      antora_metadata.sub("version: ~",
+                          "version: '#{version_sans_patch(version)}'")
+    end
+  end
+
+  def add_header_to_changelog(version)
+    update_file("CHANGELOG.md") do |changelog|
+      changelog.sub("## Master (Unreleased)\n\n",
+                    '\0' "## #{version} (#{Time.now.strftime("%F")})\n\n")
+    end
+  end
+
+  def run(release_type)
+    old_version = Bump::Bump.current
+    Bump::Bump.run(release_type, commit: false, bundle: false, tag: false)
+    new_version = Bump::Bump.current
+
+    update_cop_versions(new_version)
+    `bundle exec rake generate_cops_documentation`
+    update_docs(new_version) if %w[major minor].include?(release_type)
+    add_header_to_changelog(new_version)
+
+    puts "Changed version from #{old_version} to #{new_version}."
+  end
+end

data/tasks/new_cop.rake

@@ -0,0 +1,20 @@
+# frozen_string_literal: true
+
+desc "Generate a new cop with a template"
+task :new_cop, [:cop] do |_task, args|
+  require "rubocop"
+
+  cop_name = args.fetch(:cop) do
+    warn "usage: bundle exec rake 'new_cop[Committee/Name]'"
+    exit!
+  end
+
+  generator = RuboCop::Cop::Generator.new(cop_name)
+
+  generator.write_source
+  generator.write_spec
+  generator.inject_require(root_file_path: "lib/rubocop-committee.rb")
+  generator.inject_config(config_file_path: "config/default.yml")
+
+  puts generator.todo
+end

metadata

@@ -0,0 +1,90 @@
+--- !ruby/object:Gem::Specification
+name: rubocop-committee
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- ydah
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2022-12-28 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: |
+  Automatic committee code style checking tool.
+  A RuboCop extension focused on enforcing committee.
+email:
+- t.yudai92@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".codespellignore"
+- ".rspec"
+- ".rubocop.yml"
+- ".yamllint.yml"
+- ".yardopts"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- MIT-LICENSE.md
+- README.md
+- Rakefile
+- config/default.yml
+- docs/modules/ROOT/nav.adoc
+- docs/modules/ROOT/pages/cops.adoc
+- docs/modules/ROOT/pages/cops_committee.adoc
+- docs/modules/ROOT/pages/index.adoc
+- docs/modules/ROOT/pages/installation.adoc
+- docs/modules/ROOT/pages/usage.adoc
+- docs/modules/antora.yml
+- lib/rubocop-committee.rb
+- lib/rubocop/committee/inject.rb
+- lib/rubocop/committee/version.rb
+- lib/rubocop/cop/committee/redundant_response_status_assertions.rb
+- lib/rubocop/cop/committee/unspecified_expected_status.rb
+- tasks/cops_documentation.rake
+- tasks/cut_release.rake
+- tasks/new_cop.rake
+homepage: https://github.com/ydah/rubocop-committee
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/ydah/rubocop-committee
+  source_code_uri: https://github.com/ydah/rubocop-committee
+  changelog_uri: https://github.com/ydah/rubocop-committee/releases
+  rubygems_mfa_required: 'true'
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.3.3
+signing_key:
+specification_version: 4
+summary: Automatic committee code style checking tool.
+test_files: []