actionview-component 1.14.1 → 1.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 204fb8e9a51fffd39203ff08885333086008e513a8855b36ddbe38a8e42b72ec
-  data.tar.gz: e78a99c00889e3516552f4aa1c833be10704c32225ddcd78b713bfbae78d534c
+  metadata.gz: 38891bd3b2a3b00b7da81feb7e78fa55e5efbbf5f4bcf25abd47cf68893e7725
+  data.tar.gz: d53bc1d826b6504ea9b4fd4d5aa91362995fec79e12471c12466ea62a31c59b6
 SHA512:
-  metadata.gz: 99efaec329aeb3b4ec886eb533ebf73ec28e33931ed65e9fba80111d0403d4703a82616ac1c40bdfdf0708ee8bb60aa5dcabc9218ca0aedd8c74fb60a2ca25a8
-  data.tar.gz: 5b85c936cd7daacdf2ab71e96005444a22de2c6ff5af2d07ba412f2a6b28d5f4c828c2a9b92b84adb08816eef10492fa7a82c0c00299415a442b2f68cd7bb4da
+  metadata.gz: 3b3c2bfa37f043f19b52d9dcca5e07c8ecd7cdc3c4e06edaf775eedf5b1ced6e1a32bec284116a39222f2e67249928a175f72a75d33e84f81eb00cc918f40015
+  data.tar.gz: 626cf782c789aef2e982f13a2f8f313a3f9bf37e0bcaefc1010e9ee4f70335a6fc6062a48ca7e2d49ef4c9f0a8f4f3a9a1ed493fb5440d40da5253bf9393fb86

data/.github/PULL_REQUEST_TEMPLATE

@@ -1,4 +1,4 @@
-<!-- See https://github.com/github/actionview-component/blob/master/CONTRIBUTING.md#submitting-a-pull-request  -->
+<!-- See https://github.com/github/view_component/blob/master/CONTRIBUTING.md#submitting-a-pull-request  -->
 
 ### Summary
 

data/CHANGELOG.md

@@ -1,5 +1,29 @@
 # master
 
+# v1.15.0
+
+* Re-introduce ActionView::Component::TestHelpers.
+
+    *Joel Hawksley*
+
+* Bypass monkey patch on Rails 6.1 builds.
+
+    *Joel Hawksley*
+
+* Make `ActionView::Helpers::TagHelper` available in Previews.
+
+    ```ruby
+    def with_html_content
+      render(MyComponent.new) do
+        tag.div do
+          content_tag(:span, "Hello")
+        end
+      end
+    end
+    ```
+
+    *Sean Doyle*
+
 # v1.14.1
 
 * Fix bug where generator created invalid test code.

data/CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing
 
-[fork]: https://github.com/github/actionview-component/fork
-[pr]: https://github.com/github/actionview-component/compare
+[fork]: https://github.com/github/view_component/fork
+[pr]: https://github.com/github/view_component/compare
 [style]: https://github.com/styleguide/ruby
 [code-of-conduct]: CODE_OF_CONDUCT.md
 
@@ -38,9 +38,9 @@ If you are the current maintainer of this gem:
 1. Add version heading/entries to `CHANGELOG.md`.
 1. Make sure your local dependencies are up to date: `bundle`
 1. Ensure that tests are green: `bundle exec rake`
-1. Make a PR to github/actionview-component.
+1. Make a PR to github/view_component.
 1. Build a local gem: `gem build actionview-component.gemspec`
-1. Merge github/actionview-component PR
+1. Merge github/view_component PR
 1. Tag and push: `git tag vx.xx.xx; git push --tags`
-1. Create a GitHub release with the pushed tag (https://github.com/github/actionview-component/releases/new) and populate it with a list of the commits from `git log --pretty=format:"- %s" --reverse refs/tags/[OLD TAG]...refs/tags/[NEW TAG]`
+1. Create a GitHub release with the pushed tag (https://github.com/github/view_component/releases/new) and populate it with a list of the commits from `git log --pretty=format:"- %s" --reverse refs/tags/[OLD TAG]...refs/tags/[NEW TAG]`
 1. Push to rubygems.org -- `gem push actionview-component-VERSION.gem`

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    actionview-component (1.14.1)
+    actionview-component (1.15.0)
       capybara (>= 3)
 
 GEM

data/README.md

@@ -1,11 +1,11 @@
 # ViewComponent
 A view component framework for Rails.
 
-**Current Status**: Used in production at GitHub. Because of this, all changes will be thoroughly vetted, which could slow down the process of contributing. We will do our best to actively communicate status of pull requests with any contributors. If you have any substantial changes that you would like to make, it would be great to first [open an issue](http://github.com/github/actionview-component/issues/new) to discuss them with us.
+**Current Status**: Used in production at GitHub. Because of this, all changes will be thoroughly vetted, which could slow down the process of contributing. We will do our best to actively communicate status of pull requests with any contributors. If you have any substantial changes that you would like to make, it would be great to first [open an issue](http://github.com/github/view_component/issues/new) to discuss them with us.
 
 ## Migration in progress
 
-This gem is in the process of a name / API change from `ActionView::Component` to `ViewComponent`, see https://github.com/github/actionview-component/issues/206.
+This gem is in the process of a name / API change from `ActionView::Component` to `ViewComponent`, see https://github.com/github/view_component/issues/206.
 
 ### What's changing in the migration
 
@@ -19,7 +19,7 @@ This gem is in the process of a name / API change from `ActionView::Component` t
 1. Update components to inherit from `ViewComponent::Base`.
 1. Update component tests to inherit from `ViewComponent::TestCase`.
 1. Update component previews to inherit from `ViewComponent::Preview`.
-1. Include `ViewComponent::TestHelpers` in your test suite.
+1. Include `ViewComponent::TestHelpers` in the appropriate test helper file.
 
 ## Roadmap
 
@@ -33,20 +33,16 @@ This library is designed to integrate as seamlessly as possible with Rails, with
 
 ## Compatibility
 
-`actionview-component` is tested for compatibility with combinations of Ruby `2.5`/`2.6`/`2.7` and Rails `5.0.0`/`5.2.3`/`6.0.0`/`6.1.0.alpha`.
+`actionview-component` is tested for compatibility with combinations of Ruby `2.5`/`2.6`/`2.7` and Rails `5.0.0`/`5.2.3`/`6.0.0`/`master`.
 
 ## Installation
-Add this line to your application's Gemfile:
+
+In `Gemfile`, add:
 
 ```ruby
 gem "actionview-component"
 ```
 
-And then execute:
-```bash
-$ bundle
-```
-
 In `config/application.rb`, add:
 
 ```bash
@@ -59,49 +55,41 @@ require "view_component/engine"
 
 `ViewComponent`s are Ruby classes that are used to render views. They take data as input and return output-safe HTML. Think of them as an evolution of the presenter/decorator/view model pattern, inspired by [React Components](https://reactjs.org/docs/react-component.html).
 
-### Why components?
+Components are most effective in cases where view code is reused or benefits from being tested directly.
 
-In working on views in the Rails monolith at GitHub (which has over 3700 templates), we have run into several key pain points:
+### Why should I use components?
 
 #### Testing
 
-Currently, Rails encourages testing views via integration or system tests. This discourages us from testing our views thoroughly, due to the costly overhead of exercising the routing/controller layer, instead of just the view. It also often leads to partials being tested for each view they are included in, cheapening the benefit of DRYing up our views.
+Rails encourages testing views with integration tests. This discourages us from testing views thoroughly, due to the overhead of exercising the routing and controller layers in addition to the view.
 
-#### Code Coverage
+For partials, this means being tested for each view they are included in, reducing the benefit of reusing them.
 
-Many common Ruby code coverage tools cannot properly handle coverage of views, making it difficult to audit how thorough our tests are and leading to gaps in our test suite.
+`ViewComponent`s can be unit-tested. In the GitHub codebase, our component unit tests run in around 25 milliseconds, compared to about six seconds for integration tests.
 
 #### Data Flow
 
-Unlike a method declaration on an object, views do not declare the values they are expected to receive, making it hard to figure out what context is necessary to render them. This often leads to subtle bugs when we reuse a view across different contexts.
-
-#### Standards
+Unlike a method declaration on an object, views do not declare the values they are expected to receive, making it hard to figure out what context is necessary to render them. This often leads to subtle bugs when reusing a view in different contexts.
 
-Our views often fail even the most basic standards of code quality we expect out of our Ruby classes: long methods, deep conditional nesting, and mystery guests abound.
+By clearly defining the context necessary to render a `ViewComponent`, they're easier to reuse than partials.
 
-### What are the benefits?
+#### Standards
 
-#### Testing
+Views often fail basic Ruby code quality standards: long methods, deep conditional nesting, and mystery guests abound.
 
-`ViewComponent` allows views to be unit-tested. In the main GitHub codebase, our unit tests run in around 25ms/test, vs. ~6s/test for integration tests.
+`ViewComponent`s are Ruby objects, making it easy to follow code quality standards.
 
 #### Code Coverage
 
-`ViewComponent` is at least partially compatible with code coverage tools. We’ve seen some success with SimpleCov.
-
-#### Data flow
-
-By clearly defining the context necessary to render a component, we’ve found them to be easier to reuse than partials.
-
-### When should I use components?
+Many common Ruby code coverage tools cannot properly handle coverage of views, making it difficult to audit how thorough tests are and leading to missing coverage in test suites.
 
-Components are most effective in cases where view code is reused or needs to be tested directly.
+`ViewComponent` is at least partially compatible with code coverage tools, such as SimpleCov.
 
 ### Building components
 
 #### Conventions
 
-Components are subclasses of `ViewComponent::Base` and live in `app/components`. You may wish to create an `ApplicationComponent` that is a subclass of `ViewComponent::Base` and inherit from that instead.
+Components are subclasses of `ViewComponent::Base` and live in `app/components`. It's recommended to create an `ApplicationComponent` that is a subclass of `ViewComponent::Base` and inherit from that instead.
 
 Component class names end in -`Component`.
 
@@ -123,21 +111,17 @@ bin/rails generate component Example title content
       create  app/components/example_component.html.erb
 ```
 
-`ViewComponent` includes template generators for the `erb`, `haml`, and `slim` template engines and will use the template engine specified in your Rails config (`config.generators.template_engine`) by default.
+`ViewComponent` includes template generators for the `erb`, `haml`, and `slim` template engines and will use the template engine specified in the Rails configuration (`config.generators.template_engine`) by default.
 
-If you want to override this behavior, you can pass the template engine as an option to the generator:
+The template engine can also be passed as an option to the generator:
 
 ```bash
 bin/rails generate component Example title content --template-engine slim
-      invoke test_unit
-      create  test/components/example_component_test.rb
-      create  app/components/example_component.rb
-      create  app/components/example_component.html.slim
 ```
 
 #### Implementation
 
-A `ViewComponent` is a Ruby file and corresponding template file (in any format supported by Rails) with the same base name:
+A `ViewComponent` is a Ruby file and corresponding template file with the same base name:
 
 `app/components/test_component.rb`:
 ```ruby
@@ -145,19 +129,15 @@ class TestComponent < ViewComponent::Base
   def initialize(title:)
     @title = title
   end
-
-  private
-
-  attr_reader :title
 end
 ```
 
 `app/components/test_component.html.erb`:
 ```erb
-<span title="<%= title %>"><%= content %></span>
+<span title="<%= @title %>"><%= content %></span>
 ```
 
-We can render it in a view as:
+Which is rendered in a view as:
 
 ```erb
 <%= render(TestComponent.new(title: "my title")) do %>
@@ -171,6 +151,8 @@ Which returns:
 <span title="my title">Hello, World!</span>
 ```
 
+`ViewComponent` requires the presence of an `initialize` method in each component.
+
 #### Content Areas
 
 A component can declare additional content areas to be rendered in the component. For example:
@@ -180,11 +162,8 @@ A component can declare additional content areas to be rendered in the component
 class ModalComponent < ViewComponent::Base
   with_content_areas :header, :body
 
-  def initialize(user:)
-    @user = user
+  def initialize(*)
   end
-
-  attr_reader :user
 end
 ```
 
@@ -196,12 +175,12 @@ end
 </div>
 ```
 
-We can render it in a view as:
+Which is rendered in a view as:
 
 ```erb
-<%= render(ModalComponent.new(user: {name: 'Jane'})) do |component| %>
+<%= render(ModalComponent.new) do |component| %>
   <% component.with(:header) do %>
-      Hello <%= component.user[:name] %>
+      Hello Jane
     <% end %>
   <% component.with(:body) do %>
     <p>Have a great day.</p>
@@ -218,128 +197,14 @@ Which returns:
 </div>
 ```
 
-Content for content areas can be passed as arguments to the render method or as named blocks passed to the `with` method.
-This allows a few different combinations of ways to render the component:
-
-##### Required render argument optionally overridden or wrapped by a named block
-
-`app/components/modal_component.rb`:
-```ruby
-class ModalComponent < ViewComponent::Base
-  with_content_areas :header, :body
-
-  def initialize(header:)
-    @header = header
-  end
-end
-```
-
-```erb
-<%= render(ModalComponent.new(header: "Hi!")) do |component| %>
-  <% component.with(:header) do %>
-    <span class="help_icon"><%= component.header %></span>
-  <% end %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
-##### Required argument passed by render argument or by named block
-
-`app/components/modal_component.rb`:
-```ruby
-class ModalComponent < ViewComponent::Base
-  with_content_areas :header, :body
-
-  def initialize(header: nil)
-    @header = header
-  end
-end
-```
-
-`app/views/render_arg.html.erb`:
-```erb
-<%= render(ModalComponent.new(header: "Hi!")) do |component| %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
-`app/views/with_block.html.erb`:
-```erb
-<%= render(ModalComponent) do |component| %>
-  <% component.with(:header) do %>
-    <span class="help_icon">Hello</span>
-  <% end %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
-##### Optional argument passed by render argument, by named block, or neither
-
-`app/components/modal_component.rb`:
-```ruby
-class ModalComponent < ViewComponent::Base
-  with_content_areas :header, :body
-
-  def initialize(header: nil)
-    @header = header
-  end
-end
-```
-
-`app/components/modal_component.html.erb`:
-```erb
-<div class="modal">
-  <% if header %>
-    <div class="header"><%= header %></div>
-  <% end %>
-  <div class="body"><%= body %></div>
-</div>
-```
-
-`app/views/render_arg.html.erb`:
-```erb
-<%= render(ModalComponent.new(header: "Hi!")) do |component| %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
-`app/views/with_block.html.erb`:
-```erb
-<%= render(ModalComponent.new) do |component| %>
-  <% component.with(:header) do %>
-    <span class="help_icon">Hello</span>
-  <% end %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
-`app/views/no_header.html.erb`:
-```erb
-<%= render(ModalComponent.new) do |component| %>
-  <% component.with(:body) do %>
-    <p>Have a great day.</p>
-  <% end %>
-<% end %>
-```
-
 ### Conditional Rendering
 
-Components can implement a `#render?` method which indicates if they should be rendered, or not at all.
+Components can implement a `#render?` method to determine if they should be rendered.
 
-For example, you might have a component that displays a "Please confirm your email address" banner to users who haven't confirmed their email address. The logic for rendering the banner would need to go in either the component template:
+For example, given a component that displays a banner to users who haven't confirmed their email address, the logic for whether to render the banner would need to go in either the component template:
 
+`app/components/confirm_email_component.html.erb`
 ```
-<!-- app/components/confirm_email_component.html.erb -->
 <% if user.requires_confirmation? %>
   <div class="alert">
     Please confirm your email address.
@@ -349,17 +214,17 @@ For example, you might have a component that displays a "Please confirm your ema
 
 or the view that renders the component:
 
+`app/views/_banners.html.erb`
 ```erb
-<!-- app/views/_banners.html.erb -->
 <% if current_user.requires_confirmation? %>
   <%= render(ConfirmEmailComponent.new(user: current_user)) %>
 <% end %>
 ```
 
-The `#render?` hook allows you to move this logic into the Ruby class, leaving your views more readable and declarative in style:
+Instead, the `#render?` hook expresses this logic in the Ruby class, simplifying the view:
 
+`app/components/confirm_email_component.rb`
 ```ruby
-# app/components/confirm_email_component.rb
 class ConfirmEmailComponent < ViewComponent::Base
   def initialize(user:)
     @user = user
@@ -368,26 +233,24 @@ class ConfirmEmailComponent < ViewComponent::Base
   def render?
     @user.requires_confirmation?
   end
-
-  attr_reader :user
 end
 ```
 
+`app/components/confirm_email_component.html.erb`
 ```
-<!-- app/components/confirm_email_component.html.erb -->
 <div class="banner">
   Please confirm your email address.
 </div>
 ```
 
+`app/views/_banners.html.erb`
 ```erb
-<!-- app/views/_banners.html.erb -->
 <%= render(ConfirmEmailComponent.new(user: current_user)) %>
 ```
 
 ### Testing
 
-Components are unit tested directly. The `render_inline` test helper is compatible with Capybara matchers, allowing us to test the component above as:
+Unit test components directly, using the `render_inline` test helper and Capybara matchers:
 
 ```ruby
 require "view_component/test_case"
@@ -401,11 +264,9 @@ class MyComponentTest < ViewComponent::TestCase
 end
 ```
 
-In general, we’ve found it makes the most sense to test components based on their rendered HTML.
-
 #### Action Pack Variants
 
-To test a specific variant you can wrap your test with the `with_variant` helper method as:
+Use the `with_variant` helper to test specific variants:
 
 ```ruby
 test "render component for tablet" do
@@ -418,14 +279,10 @@ end
 ```
 
 ### Previewing Components
-`ViewComponent::Preview` provides a way to see how components look by visiting a special URL that renders them.
-In the previous example, the preview class for `TestComponent` would be called `TestComponentPreview` and located in `test/components/previews/test_component_preview.rb`.
-To see the preview of the component with a given title, implement a method that renders the component.
-You can define as many examples as you want:
+`ViewComponent::Preview`, like `ActionMailer::Preview`, provides a way to preview components in isolation:
 
+`test/components/previews/test_component_preview.rb`
 ```ruby
-# test/components/previews/test_component_preview.rb
-
 class TestComponentPreview < ViewComponent::Preview
   def with_default_title
     render(TestComponent.new(title: "Test component default"))
@@ -434,17 +291,33 @@ class TestComponentPreview < ViewComponent::Preview
   def with_long_title
     render(TestComponent.new(title: "This is a really long title to see how the component renders this"))
   end
+
+  def with_content_block
+    render(TestComponent.new(title: "This component accepts a block of content") do
+      tag.div do
+        content_tag(:span, "Hello")
+      end
+    end
+  end
 end
 ```
 
-The previews will be available in <http://localhost:3000/rails/components/test_component/with_default_title>
-and <http://localhost:3000/rails/components/test_component/with_long_title>.
+Which generates <http://localhost:3000/rails/components/test_component/with_default_title>,
+<http://localhost:3000/rails/components/test_component/with_long_title>,
+and <http://localhost:3000/rails/components/test_component/with_content_block>.
 
-Previews use the application layout by default, but you can also use other layouts from your app:
+The `ViewComponent::Preview` base class includes
+[`ActionView::Helpers::TagHelper`][tag-helper], which provides the [`tag`][tag]
+and [`content_tag`][content_tag] view helper methods.
 
-```ruby
-# test/components/previews/test_component_preview.rb
+[tag-helper]: https://api.rubyonrails.org/classes/ActionView/Helpers/TagHelper.html
+[tag]: https://api.rubyonrails.org/classes/ActionView/Helpers/TagHelper.html#method-i-tag
+[content_tag]: https://api.rubyonrails.org/classes/ActionView/Helpers/TagHelper.html#method-i-content_tag
 
+Previews default to the application layout, but can be overridden:
+
+`test/components/previews/test_component_preview.rb`
+```ruby
 class TestComponentPreview < ViewComponent::Preview
   layout "admin"
 
@@ -452,52 +325,46 @@ class TestComponentPreview < ViewComponent::Preview
 end
 ```
 
-By default, the preview classes live in `test/components/previews`.
-This can be configured using the `preview_path` option.
-For example, if you want to use `lib/component_previews`, set the following in `config/application.rb`:
+Preview classes live in `test/components/previews`, can be configured using the `preview_path` option.
 
+To use `lib/component_previews`:
+
+`config/application.rb`
 ```ruby
 config.action_view_component.preview_path = "#{Rails.root}/lib/component_previews"
 ```
 
 #### Configuring TestController
 
-By default components tests and previews expect your Rails project to contain an `ApplicationController` class from which Controller classes inherit.
-This can be configured using the `test_controller` option.
-For example, if your controllers inherit from `BaseController`, set the following in `config/application.rb`:
+Component tests and previews assume the existence of an `ApplicationController` class, be can beconfigured using the `test_controller` option:
 
+`config/application.rb`
 ```ruby
 config.action_view_component.test_controller = "BaseController"
 ```
 
 ### Setting up RSpec
 
-If you're using RSpec, you can configure component specs to have access to test helpers. Add the following to
-`spec/rails_helper.rb`:
+To use RSpec, add the following:
 
+`spec/rails_helper.rb`
 ```ruby
 require "view_component/test_helpers"
 
 RSpec.configure do |config|
-    # ...
-
-    # Ensure that the test helpers are available in component specs
-    config.include ViewComponent::TestHelpers, type: :component
+  config.include ViewComponent::TestHelpers, type: :component
 end
 ```
 
-Specs created by the generator should now have access to test helpers like `render_inline`.
+Specs created by the generator have access to test helpers like `render_inline`.
 
-To use component previews, set the following in `config/application.rb`:
+To use component previews:
 
+`config/application.rb`
 ```ruby
 config.action_view_component.preview_path = "#{Rails.root}/spec/components/previews"
 ```
 
-### Initializer requirement
-
-`ViewComponent` requires the presence of an `initialize` method in each component.
-
 ## Frequently Asked Questions
 
 ### Can I use other templating languages besides ERB?
@@ -523,11 +390,11 @@ Inline templates have been removed (for now) due to concerns raised by [@soutaro
 - [Introducing ActionView::Component with Joel Hawksley, Ruby on Rails Podcast](http://5by5.tv/rubyonrails/276)
 - [Rails to Introduce View Components, Dev.to](https://dev.to/andy/rails-to-introduce-view-components-3ome)
 - [ActionView::Components in Rails 6.1, Drifting Ruby](https://www.driftingruby.com/episodes/actionview-components-in-rails-6-1)
-- [Demo repository, actionview-component-demo](https://github.com/joelhawksley/actionview-component-demo)
+- [Demo repository, view-component-demo](https://github.com/joelhawksley/view-component-demo)
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/github/actionview-component. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. We recommend reading the [contributing guide](./CONTRIBUTING.md) as well.
+Bug reports and pull requests are welcome on GitHub at https://github.com/github/view_component. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. We recommend reading the [contributing guide](./CONTRIBUTING.md) as well.
 
 ## Contributors
 
@@ -563,6 +430,11 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/github
 |@blakewilliams|
 |Boston, MA|
 
+|<img src="https://avatars.githubusercontent.com/seanpdoyle?s=256" alt="seanpdoyle" width="128" />|
+|:---:|
+|@seanpdoyle|
+|New York, NY|
+
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/actionview-component.gemspec

@@ -9,11 +9,11 @@ Gem::Specification.new do |spec|
   spec.name          = "actionview-component"
   spec.version       = ViewComponent::VERSION::STRING
   spec.authors       = ["GitHub Open Source"]
-  spec.email         = ["opensource+actionview-component@github.com"]
+  spec.email         = ["opensource+view_component@github.com"]
 
   spec.summary       = %q{View components for Rails}
-  spec.description   = %q{View components for Rails, intended for upstreaming in Rails 6.1}
-  spec.homepage      = "https://github.com/github/actionview-component"
+  spec.description   = %q{View components for Rails}
+  spec.homepage      = "https://github.com/github/view_component"
   spec.license       = "MIT"
 
   # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'

data/docs/case-studies/jellyswitch.md

@@ -0,0 +1,76 @@
+Name: Dave Paola
+
+Github Handle: [@dpaola2](https://github.com/dpaola2)
+
+[Jellyswitch](https://www.jellyswitch.com) is a coworking space management platform
+
+In response to [this tweet](https://twitter.com/joelhawksley/status/1232674647327547394):
+
+I recently began refactoring many of my partials into components. Along the way I discovered an interesting use case, which was to componentize the various bootstrap components I was already using.
+
+Some examples:
+
+- I've componentized the specific layout that I've designed using the grid system. I have defined a `FullWidthLayout` component that wraps its contents in the correct classes to give my layout a good design on both mobile and desktop. (On desktop, there is a sidebar, and on mobile, the sidebar floats on top in a collapsed fashion.)
+- [Modals](https://getbootstrap.com/docs/4.4/components/modal/) are now componentized and accept arguments. I had them as partials before, but having ruby classes is an upgrade.
+- [Breadcrumbs](https://getbootstrap.com/docs/4.4/components/breadcrumb/) same as above.
+
+Here's one that I use a LOT: `OnOffSwitch`:
+
+```ruby
+class OnOffSwitch < ApplicationComponent
+  def initialize(predicate:, path:, disabled: false, label: nil)
+    @predicate = predicate
+    @path = path
+    @disabled = disabled
+    @label = label
+  end
+
+  private
+
+  attr_reader :predicate, :path, :disabled, :label
+  
+  def icon_class
+    if predicate
+      "fas fa-toggle-on"
+    else
+      "fas fa-toggle-off"
+    end
+  end
+end
+```
+
+```erb
+<div class="d-flex align-items-center">
+  <% if !disabled %>
+    <%= link_to path, class: "text-body", remote: true do %>
+      <span style="font-size: 20pt">
+        <% if predicate %>
+          <span class="text-success">
+            <i class="<%= icon_class %>"></i>
+          </span>
+        <% else %>
+          <span class="text-danger">
+            <i class="<%= icon_class %>"></i>
+          </span>
+        <% end %>
+      </span>
+    <% end %>
+  <% else %>
+    <span style="font-size: 20pt">
+      <span class="text-muted">
+        <i class="<%= icon_class %>"></i>
+      </span>
+    </span>
+  <% end %>
+  &nbsp;
+  <%= content %>
+</div>
+```
+
+Here is an example of how this looks:
+
+<img width="653" alt="Screenshot 2020-02-26 08 34 07" src="https://user-images.githubusercontent.com/150509/75365920-cbfb9500-5872-11ea-8234-f1343629a462.png">
+
+I have found that refactoring complex views is made easier and faster by first putting them into a component, extracting the conditionals and other logic into private methods and proceeding from there. And I wind up with a very nice set of well-factored components and sub-components, with argument lists and validations and so on. I think the rails community is really going to benefit from this library, and I'm hugely appreciative of y'all's efforts on it!
+
+I plan to release an early version of the bootstrap components we've developed at some point in the near future. I would love to collaborate and learn the most appropriate way to structure that contribution.

data/lib/action_view/component/test_case.rb

@@ -2,7 +2,8 @@
 
 module ActionView
   module Component
-    class TestCase < ViewComponent::TestCase
+    class TestCase
+      include ActionView::Component::TestHelpers
     end
   end
 end

data/lib/action_view/component/test_helpers.rb

@@ -0,0 +1,17 @@
+# frozen_string_literal: true
+
+module ActionView
+  module Component
+    module TestHelpers
+      include ViewComponent::TestHelpers
+
+      def render_component(component, **args, &block)
+        ActiveSupport::Deprecation.warn(
+          "`render_component` has been deprecated in favor of `render_inline`, and will be removed in v2.0.0."
+        )
+
+        render_inline(component, args, &block)
+      end
+    end
+  end
+end

data/lib/view_component.rb

@@ -23,6 +23,7 @@ module ActionView
     autoload :Base
     autoload :Preview
     autoload :TestCase
+    autoload :TestHelpers
   end
 end
 

data/lib/view_component/preview.rb

@@ -4,6 +4,7 @@ require "active_support/descendants_tracker"
 
 module ViewComponent # :nodoc:
   class Preview
+    include ActionView::Helpers::TagHelper
     extend ActiveSupport::DescendantsTracker
 
     def render(component, **args, &block)

data/lib/view_component/render_monkey_patch.rb

@@ -3,7 +3,7 @@
 module ViewComponent
   module RenderMonkeyPatch # :nodoc:
     def render(options = {}, args = {}, &block)
-      if options.respond_to?(:render_in)
+      if options.respond_to?(:render_in) && Rails.version.to_f < 6.1
         options.render_in(self, &block)
       elsif options.is_a?(Class) && options < ActionView::Component::Base
         ActiveSupport::Deprecation.warn(

data/lib/view_component/rendering_monkey_patch.rb

@@ -3,7 +3,7 @@
 module ViewComponent
   module RenderingMonkeyPatch # :nodoc:
     def render(options = {}, args = {})
-      if options.respond_to?(:render_in)
+      if options.respond_to?(:render_in) && Rails.version.to_f < 6.1
         self.response_body = options.render_in(self.view_context)
       else
         super

data/lib/view_component/test_helpers.rb

@@ -24,14 +24,6 @@ module ViewComponent
       @request ||= ActionDispatch::TestRequest.create
     end
 
-    def render_component(component, **args, &block)
-      ActiveSupport::Deprecation.warn(
-        "`render_component` has been deprecated in favor of `render_inline`, and will be removed in v2.0.0."
-      )
-
-      render_inline(component, args, &block)
-    end
-
     def with_variant(variant)
       old_variants = controller.view_context.lookup_context.variants
 

data/lib/view_component/version.rb

@@ -3,8 +3,8 @@
 module ViewComponent
   module VERSION
     MAJOR = 1
-    MINOR = 14
-    PATCH = 1
+    MINOR = 15
+    PATCH = 0
 
     STRING = [MAJOR, MINOR, PATCH].join(".")
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: actionview-component
 version: !ruby/object:Gem::Version
-  version: 1.14.1
+  version: 1.15.0
 platform: ruby
 authors:
 - GitHub Open Source
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-03-03 00:00:00.000000000 Z
+date: 2020-03-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: capybara
@@ -136,9 +136,9 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 0.13.0
-description: View components for Rails, intended for upstreaming in Rails 6.1
+description: View components for Rails
 email:
-- opensource+actionview-component@github.com
+- opensource+view_component@github.com
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -158,11 +158,13 @@ files:
 - Rakefile
 - actionview-component.gemspec
 - app/controllers/rails/components_controller.rb
+- docs/case-studies/jellyswitch.md
 - lib/action_view/component.rb
 - lib/action_view/component/base.rb
 - lib/action_view/component/preview.rb
 - lib/action_view/component/railtie.rb
 - lib/action_view/component/test_case.rb
+- lib/action_view/component/test_helpers.rb
 - lib/rails/generators/component/USAGE
 - lib/rails/generators/component/component_generator.rb
 - lib/rails/generators/component/templates/component.rb.tt
@@ -197,7 +199,7 @@ files:
 - script/install
 - script/release
 - script/test
-homepage: https://github.com/github/actionview-component
+homepage: https://github.com/github/view_component
 licenses:
 - MIT
 metadata: