modular_routes 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 954ed3363ece12cbe51eca5df6783f6066d49b3b5320dbcf7e9e10d0acf4bc05
+  data.tar.gz: 80fd6d08afa02b8502999c5ed5d37ca6104b64ef4714464f6adb0407d00fb364
+SHA512:
+  metadata.gz: 8415af3f02b945890d14770c4e92d1bb2dfb3779773bdff86f6a87aa3e1417cb1c67fb6710c581b33031dc6bdf350fce97e15aa245c2fb7f07327e031c942397
+  data.tar.gz: 6aad4a4706157f87818541122dc520f83eb22eca43167d08162b40eb575546c82e674c90d83d0882be7aa1d98e82f09429e922aa1aaac4dfbc514710f878c73e

data/.editorconfig

@@ -0,0 +1,10 @@
+# editorconfig.org
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

data/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on: [push, pull_request]
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby: ["2.7", "3.0"]
+    steps:
+      - name: Clone
+        uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+      - name: Install gems
+        run: |
+          gem install bundler -v 2.2.15
+          bundle install
+      - name: Run the specs task
+        env:
+          COVERAGE: "true"
+        run: |
+          bundle exec rake spec

data/.github/workflows/coverage.yml

@@ -0,0 +1,24 @@
+name: Coverage
+
+on: [push, pull_request]
+
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Clone
+        uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.0
+          bundler-cache: true
+      - name: Install gems
+        run: |
+          gem install bundler -v 2.2.15
+          bundle install
+      - name: Run the coverage task
+        env:
+          COVERAGE: "true"
+        run: |
+          bundle exec rake spec

data/.github/workflows/rubocop.yml

@@ -0,0 +1,22 @@
+name: RuboCop
+
+on: [push, pull_request]
+
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Clone
+        uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.0
+          bundler-cache: true
+      - name: Install gems
+        run: |
+          gem install bundler -v 2.2.15
+          bundle install
+      - name: Run the rubocop task
+        run: |
+          bundle exec rake rubocop

data/.gitignore

@@ -0,0 +1,12 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/spec/internal/db/*.sqlite
+/tmp/
+Gemfile.lock
+# rspec failure tracking
+.rspec_status

data/.rspec

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

data/.rubocop.yml

@@ -0,0 +1,41 @@
+inherit_gem:
+  rubocop-shopify: rubocop.yml
+
+require:
+  - rubocop-performance
+
+AllCops:
+  TargetRubyVersion: 2.7
+  NewCops: enable
+# Metrics/BlockLength:
+#   Exclude:
+#     - "**/*_spec.rb"
+#     - "**/spec/**/*.rb"
+
+# Metrics/AbcSize:
+#   Max: 18
+#   Exclude:
+#     - "**/*_spec.rb"
+#     - "**/spec/**/*.rb"
+
+# Metrics/ModuleLength:
+#   Exclude:
+#     - "**/*_spec.rb"
+#     - "**/spec/**/*.rb"
+
+# RSpec/MultipleExpectations:
+#   Exclude:
+#     - "**/requests/**/*_spec.rb"
+
+# RSpec/AnyInstance:
+#   Exclude:
+#     - spec/support/**.rb
+
+# Style/AccessorGrouping:
+#   EnforcedStyle: separated
+
+# Style/SymbolArray:
+#   EnforcedStyle: brackets
+
+# Style/AccessModifierDeclarations:
+#   EnforcedStyle: inline

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2021-05-24
+
+- Initial release

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 contact@vitoravelino.me. 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).
+
+[homepage]: https://www.contributor-covenant.org
+
+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.

data/Gemfile

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gemspec

data/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2021 Vítor Avelino
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,349 @@
+[gem]: https://rubygems.org/gems/modular_routes
+[ci]: https://github.com/vitoravelino/modular_routes/actions/workflows/ci.yml
+[coverage]: https://github.com/vitoravelino/modular_routes/actions/workflows/coverage.yml
+[codeclimate]: https://codeclimate.com/github/vitoravelino/modular_routes
+
+# Modular Routes
+
+_A simple way of having dedicated controllers for each of your route actions in Rails._
+
+[![gem version](https://img.shields.io/gem/v/modular_routes)][gem]
+[![CI](https://github.com/vitoravelino/modular_routes/actions/workflows/ci.yml/badge.svg)][ci]
+[![Coverage](https://github.com/vitoravelino/modular_routes/actions/workflows/coverage.yml/badge.svg)][coverage]
+[![Maintainability](https://img.shields.io/codeclimate/maintainability/vitoravelino/modular_routes)][codeclimate]
+
+If you've ever used [Hanami routes](https://guides.hanamirb.org/v1.3/routing/restful-resources/) or already use dedicated controllers for each route action, this gem might be useful.
+
+Disclaimer: There's no better/worse nor right/wrong approach, it's up to you to decide how you prefer to organize the controllers and routes of your application.
+
+## Motivation
+
+Let's imagine that you have to design a full RESTful resource named `articles` with some custom routes like the table below
+
+| HTTP Verb | Path                  |
+| --------- | --------------------- |
+| GET       | /articles             |
+| GET       | /articles/new         |
+| POST      | /articles             |
+| GET       | /articles/:id         |
+| GET       | /articles/:id/edit    |
+| PATCH/PUT | /articles/:id         |
+| DELETE    | /articles/:id         |
+| GET       | /articles/stats       |
+| POST      | /articles/:id/archive |
+
+How would you organize the controllers and routes of this application?
+
+The most common approach is to have all the actions (RESTful and customs) in the same controller.
+
+```ruby
+# routes.rb
+
+resources :articles do
+  get  :stats,   on: :collection
+  post :archive, on: :member
+end
+
+# articles_controller.rb
+
+class ArticlesController
+  def index
+    # ...
+  end
+
+  def create
+    # ...
+  end
+
+  # other actions...
+
+  def stats
+    # ...
+  end
+
+  def archive
+    # ...
+  end
+end
+```
+
+The reason I don't like this approach is that you can end up with a lot of code that are not related to each other in the same file. You can still have it all organized but I believe that it could be better.
+
+[DHH](http://jeromedalbert.com/how-dhh-organizes-his-rails-controllers/) prefers to keep the RESTful actions (index, new, edit, show, create, update, destroy) inside the same controller and the custom ones in dedicated controllers.
+
+One way of representing that would be
+
+```ruby
+# routes.rb
+
+resources :articles do
+  get  :stats,   on: :collection, controller: 'articles/stats'
+  post :archive, on: :member,     controller: 'articles/archive'
+end
+
+# articles_controller.rb
+
+class ArticlesController
+  def index
+    # ...
+  end
+
+  def create
+    # ...
+  end
+
+  # other actions...
+end
+
+# articles/archive_controller.rb
+
+class Articles::ArchiveController
+  def archive
+  end
+end
+
+# articles/stats_controller.rb
+
+class Articles::StatsController
+  def stats
+  end
+end
+```
+
+This approach is better than the previous one because it restricts the main controller file to contain only the RESTful actions. Additional routes would require you to create a dedicated controller to handle that individually.
+
+Another approach (and what I personally prefer) is to have one controller per route. What it was done for `archive` and `stats` routes would also be applied to all the RESTful routes.
+
+The files would be organized inside `articles/` folder that would act as a namespace
+
+```
+app/
+└── controllers/
+    └── articles/
+        ├── archive_controller.rb
+        ├── create_controller.rb
+        ├── destroy_controller.rb
+        ├── edit_controller.rb
+        ├── index_controller.rb
+        ├── new_controller.rb
+        ├── show_controller.rb
+        ├── stats_controller.rb
+        └── update_controller.rb
+```
+
+And the controllers would have one single action named `call` like
+
+```ruby
+# articles/index_controller.rb
+
+class Articles::IndexController
+  def call
+  end
+end
+
+# articles/archive_controller.rb
+
+class Articles::ArchiveController
+  def call
+  end
+end
+```
+
+Here are two ways of representing what was explained above:
+
+```ruby
+scope module: :articles, path: '/articles' do
+  get    '/',        to: 'index#call', as: 'articles'
+  post   '/',        to: 'create#call'
+
+  get    'new',      to: 'new#call',  as: 'new_article'
+  get    ':id/edit', to: 'edit#call', as: 'edit_article'
+  get    ':id',      to: 'show#call', as: 'article'
+  patch  ':id',      to: 'update#call'
+  put    ':id',      to: 'update#call'
+  delete ':id',      to: 'destroy#call'
+
+  post 'stats',       to: 'stats#call',   as: 'stats_articles'
+  post ':id/archive', to: 'archive#call', as: 'archive_article'
+end
+```
+
+or
+
+```ruby
+resources :articles, module: :articles, only: [] do
+  collection do
+    get  :index,  to: 'index#call'
+    post :create, to: 'create#call'
+    post :stats,  to: 'stats#call'
+  end
+
+  new do
+    get :new, to: 'new#call'
+  end
+
+  member do
+    get    :edit,    to: 'edit#call'
+    get    :show,    to: 'show#call'
+    patch  :update,  to: 'update#call'
+    put    :update,  to: 'update#call'
+    delete :destroy, to: 'destroy#call'
+    post   :archive, to: 'archive#call'
+  end
+end
+```
+
+This is the best approach in my opinion because your controller will contain only code related to that specific route action. It will also be easier to test and maintain the code.
+
+If you've decided to go with the last approach, unless you organizes your routes in [separated files](https://guides.rubyonrails.org/routing.html#breaking-up-very-large-route-file-into-multiple-small-ones), your `config/routes.rb` might get really messy as your application grows due to verbosity.
+
+So, what if we had a simpler way of doing all of that? Let's take a look at how modular routes can help us.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem "modular_routes"
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install modular_routes
+
+## Usage
+
+`modular_route` uses `resource` and `resources` route helpers behind the scenes. So you can pretty much use almost everything you already use with them except for a few [limitations](#limitations) that will be explained later.
+
+For the same example used in the [motivation](#motivation) section, using modular routes we now have
+
+```ruby
+# routes.rb
+
+modular_route resources: :articles, all: true do
+  collection do
+    post :stats
+  end
+
+  member do
+    post :archive
+  end
+end
+```
+
+or to be shorter
+
+```ruby
+# routes.rb
+
+modular_route resources: :articles, all: true do
+  post :stats,   on: :collection
+  post :archive, on: :member
+end
+```
+
+The only mandatory option to use `modular_route` helper is to pass `:resources` or `:resource` as key with the following resource name.
+
+To generate all RESTful routes, you must pass `all: true`. Otherwise nothing will happen unless you pass a block with additional routes.
+
+The output routes for the code above would be
+
+| HTTP Verb | Path                  | Controller#Action     | Named Route Helper        |
+| --------- | --------------------- | --------------------- | ------------------------- |
+| GET       | /articles             | articles/index#call   | articles_path             |
+| GET       | /articles/new         | articles/new#call     | new_article_path          |
+| POST      | /articles             | articles/create#call  | articles_path             |
+| GET       | /articles/:id         | articles/show#call    | articles_path(:id)        |
+| GET       | /articles/:id/edit    | articles/edit#call    | edit_articles_path(:id)   |
+| PATCH/PUT | /articles/:id         | articles/update#call  | articles_path(:id)        |
+| DELETE    | /articles/:id         | articles/destroy#call | articles_path(:id)        |
+| POST      | /articles/stats       | articles/stats#call   | stats_articles_path(:id)  |
+| POST      | /articles/:id/archive | articles/archive#call | archive_article_path(:id) |
+
+### Restricting routes
+
+You can restrict the routes for the RESTful with `:only` and `:except` similar to what you can do in Rails by default.
+
+```ruby
+modular_route resources: :articles, only: [:index, :show]
+```
+
+```ruby
+modular_route resources: :articles, except: [:destroy]
+```
+
+### Renaming paths
+
+As in Rails you can simply use `:path` attribute.
+
+```ruby
+modular_route resources: :articles, all: true, path: 'posts'
+```
+
+is going to produce
+
+| HTTP Verb | Path            | Controller#Action     | Named Route Helper     |
+| --------- | --------------- | --------------------- | ---------------------- |
+| GET       | /posts          | articles/index#call   | articles_path          |
+| GET       | /posts/new      | articles/new#call     | new_article_path       |
+| POST      | /posts          | articles/create#call  | articles_path          |
+| GET       | /posts/:id      | articles/show#call    | article_path(:id)      |
+| GET       | /posts/:id/edit | articles/edit#call    | edit_article_path(:id) |
+| PATCH/PUT | /posts/:id      | articles/update#call  | article_path(:id)      |
+| DELETE    | /posts/:id      | articles/destroy#call | article_path(:id)      |
+
+### API mode
+
+If your Rails app is with API only mode, then `:edit` and `:new` actions won't be applied.
+
+### Limitations
+
+Some of the restrictions are:
+
+- `concerns` won't work
+- `constraints` only as option and not block
+- no support for nesting
+
+#### Nesting
+
+Even without nesting support you can emulate what the expected behaviour would be mixing `namespace` and `path` as detailed below
+
+```ruby
+namespace :books, path: 'books/:book_id' do
+  modular_route resources: :reviews, all: true
+end
+```
+
+The output routes for that would be
+
+| HTTP Verb | Path                             | Controller#Action          | Named Route Helper              |
+| --------- | -------------------------------- | -------------------------- | ------------------------------- |
+| GET       | /books/:book_id/reviews          | books/reviews/index#call   | books_reviews_path              |
+| GET       | /books/:book_id/reviews/new      | books/reviews/new#call     | new_articles_reviews_path       |
+| POST      | /books/:book_id/reviews          | books/reviews/create#call  | books_reviews_path              |
+| GET       | /books/:book_id/reviews/:id      | books/reviews/show#call    | books_reviews_path(:id)         |
+| GET       | /books/:book_id/reviews/:id/edit | books/reviews/edit#call    | edit_articles_reviews_path(:id) |
+| PATCH/PUT | /books/:book_id/reviews/:id      | books/reviews/update#call  | books_reviews_path(:id)         |
+| DELETE    | /books/:book_id/reviews/:id      | books/reviews/destroy#call | books_reviews_path(:id)         |
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/vitoravelino/modular_routes. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/vitoravelino/modular_routes/blob/master/CODE_OF_CONDUCT.md).
+
+## Code of Conduct
+
+Everyone interacting in the ModularRoutes project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/vitoravelino/modular_routes/blob/master/CODE_OF_CONDUCT.md).
+
+## Licensing
+
+Modular Routes is licensed under the Apache License, Version 2.0. See [LICENSE](https://github.com/vitoravelino/modular_routes/blob/master/LICENSE) for the full license text.

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: [:spec, :rubocop]

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "modular_routes"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don"t forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/modular_routes.rb

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require "action_dispatch"
+
+require_relative "modular_routes/builder"
+require_relative "modular_routes/extension"
+require_relative "modular_routes/options"
+require_relative "modular_routes/route/non_restful"
+require_relative "modular_routes/route/restful"
+require_relative "modular_routes/version"
+
+module ModularRoutes
+  ActionDispatch::Routing::Mapper.include(Extension)
+end

data/lib/modular_routes/builder.rb

@@ -0,0 +1,45 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  class Builder
+    HTTP_METHODS = [:post, :get, :put, :patch, :delete].freeze
+
+    attr_reader :routes
+
+    def initialize(route_options)
+      @route_options = route_options
+      @routes = build_resource_routes
+    end
+
+    HTTP_METHODS.each do |method|
+      define_method(method) do |action, options = {}|
+        mutable_options = { on: @on }
+        merged_options = mutable_options.merge(options)
+
+        @routes.unshift(Route::NonRestful.new(method, action, merged_options, @route_options))
+      end
+    end
+
+    def collection
+      @on = :collection
+      yield
+    ensure
+      @on = nil
+    end
+
+    def member
+      @on = :member
+      yield
+    ensure
+      @on = nil
+    end
+
+    private def build_resource_routes
+      @route_options.actions.map { |action| build_resource_route(action) }
+    end
+
+    private def build_resource_route(action)
+      Route::Restful.new(@route_options, action)
+    end
+  end
+end

data/lib/modular_routes/extension.rb

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  module Extension
+    def modular_route(options, &block)
+      route_options = Options.new(options.merge(api_only: api_only?))
+      route_builder = Builder.new(route_options)
+      route_builder.instance_eval(&block) if block
+      route_builder.routes.each { |route| route.apply(self) }
+    end
+  end
+end

data/lib/modular_routes/options.rb

@@ -0,0 +1,50 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  class Options
+    attr_reader :method
+    attr_reader :module
+    attr_reader :resource
+    attr_reader :options
+
+    def initialize(options)
+      @options = options
+      @method = extract_resource_method
+      @resource = @options.delete(@method)
+      @module = @options.fetch(:module, @resource)
+      @api = @options.delete(:api_only) { false }
+
+      @only = @options.delete(:only)
+      @except = @options.delete(:except)
+      @all = @options.delete(:all)
+    end
+
+    def singular?
+      method == :resource
+    end
+
+    def actions
+      return default_actions if @all
+
+      return default_actions - Array(@except) if @except
+
+      Array(@only)
+    end
+
+    private def default_actions
+      actions = [:index, :create, :new, :edit, :show, :update, :destroy]
+
+      actions -= [:index] if singular?
+      actions -= [:edit, :new] if @api
+
+      actions
+    end
+
+    private def extract_resource_method
+      return :resource if options.include?(:resource)
+      return :resources if options.include?(:resources)
+
+      raise ArgumentError, "you must specify :resource or :resources for `modular_route`"
+    end
+  end
+end

data/lib/modular_routes/route/non_restful.rb

@@ -0,0 +1,48 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  module Route
+    class NonRestful
+      attr_reader :http_method
+      attr_reader :action
+
+      def initialize(http_method, action, options, scope_options)
+        @http_method = http_method
+        @action = action
+        @options = options
+        @scope_options = scope_options
+
+        unless @options.fetch(:on, nil)
+          raise ArgumentError,
+            "Non-RESTful route should be declared inside `member`/`collection` block or using `:on` key"
+        end
+      end
+
+      def apply(mapper)
+        method = @scope_options.method
+        resource = @scope_options.resource
+
+        mapper.public_send(method, resource, resource_options) do
+          mapper.public_send(http_method, action, options)
+        end
+      end
+
+      private def resource_options
+        immutable_options = {
+          only: [],
+          module: @scope_options.module,
+        }
+
+        @scope_options.options.merge(immutable_options)
+      end
+
+      private def options
+        mutable_options = {
+          to: "#{action}#call",
+        }
+
+        mutable_options.merge(@options)
+      end
+    end
+  end
+end

data/lib/modular_routes/route/restful.rb

@@ -0,0 +1,31 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  module Route
+    class Restful
+      def initialize(route_options, action)
+        @module = route_options.module
+        @resource = route_options.resource
+        @options = route_options.options
+        @method = route_options.method
+        @action = action
+      end
+
+      def apply(mapper)
+        mapper.public_send(@method, @resource, resource_options)
+      end
+
+      private def resource_options
+        immutable_options = {
+          controller: @action,
+          only: @action,
+          action: :call,
+        }
+
+        mutable_options = { module: @module }
+
+        mutable_options.merge(@options).merge(immutable_options)
+      end
+    end
+  end
+end

data/lib/modular_routes/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module ModularRoutes
+  VERSION = "0.1.1"
+end

data/modular_routes.gemspec

@@ -0,0 +1,44 @@
+# frozen_string_literal: true
+
+require_relative "lib/modular_routes/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "modular_routes"
+  spec.version       = ModularRoutes::VERSION
+  spec.authors       = ["Vítor Avelino"]
+  spec.email         = ["contact@vitoravelino.me"]
+
+  spec.summary       = "A simple way of having dedicated controllers for each of your route actions in Rails"
+  spec.description   = spec.summary
+  spec.homepage      = "https://github.com/vitoravelino/modular_routes"
+
+  spec.required_ruby_version = Gem::Requirement.new(">= 2.7.0")
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = spec.homepage
+  spec.metadata["changelog_uri"] = spec.homepage
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(File.expand_path(__dir__)) do
+    %x(git ls-files -z).split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+  spec.add_dependency("rails")
+
+  spec.add_development_dependency("combustion")
+  spec.add_development_dependency("rspec-rails")
+  spec.add_development_dependency("rubocop-performance")
+  spec.add_development_dependency("rubocop-rspec")
+  spec.add_development_dependency("rubocop-shopify")
+  spec.add_development_dependency("rubycritic")
+  spec.add_development_dependency("sqlite3")
+
+  # For more information and examples about making a new gem, checkout our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

metadata

@@ -0,0 +1,182 @@
+--- !ruby/object:Gem::Specification
+name: modular_routes
+version: !ruby/object:Gem::Version
+  version: 0.1.1
+platform: ruby
+authors:
+- Vítor Avelino
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2021-07-15 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rails
+  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'
+- !ruby/object:Gem::Dependency
+  name: combustion
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rspec-rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubocop-performance
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubocop-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubocop-shopify
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubycritic
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: sqlite3
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: A simple way of having dedicated controllers for each of your route actions
+  in Rails
+email:
+- contact@vitoravelino.me
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".editorconfig"
+- ".github/workflows/ci.yml"
+- ".github/workflows/coverage.yml"
+- ".github/workflows/rubocop.yml"
+- ".gitignore"
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- LICENSE
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/modular_routes.rb
+- lib/modular_routes/builder.rb
+- lib/modular_routes/extension.rb
+- lib/modular_routes/options.rb
+- lib/modular_routes/route/non_restful.rb
+- lib/modular_routes/route/restful.rb
+- lib/modular_routes/version.rb
+- modular_routes.gemspec
+homepage: https://github.com/vitoravelino/modular_routes
+licenses: []
+metadata:
+  homepage_uri: https://github.com/vitoravelino/modular_routes
+  source_code_uri: https://github.com/vitoravelino/modular_routes
+  changelog_uri: https://github.com/vitoravelino/modular_routes
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.7.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.15
+signing_key:
+specification_version: 4
+summary: A simple way of having dedicated controllers for each of your route actions
+  in Rails
+test_files: []