Link Search Menu Expand Document

Building ViewComponents


Components are subclasses of ViewComponent::Base and live in app/components. It’s common practice to create and inherit from an ApplicationComponent that is a subclass of ViewComponent::Base.

Component names end in -Component.

Component module names are plural, as for controllers and jobs: Users::AvatarComponent

Name components for what they render, not what they accept. (AvatarComponent instead of UserComponent)

Quick start

Use the component generator to create a new ViewComponent.

The generator accepts a component name and a list of arguments:

bin/rails generate component Example title

      invoke  test_unit
      create  test/components/example_component_test.rb
      create  app/components/example_component.rb
      create  app/components/example_component.html.erb

ViewComponent includes template generators for the erb, haml, and slim template engines and will default to the template engine specified in config.generators.template_engine.

The template engine can also be passed as an option to the generator:

bin/rails generate component Example title --template-engine slim

To generate a preview, pass the --preview option:

bin/rails generate component Example title --preview


A ViewComponent is a Ruby file and corresponding template file with the same base name:


class ExampleComponent < ViewComponent::Base
  def initialize(title:)
    @title = title


<span title="<%= @title %>"><%= content %></span>

Content passed to a ViewComponent as a block is captured and assigned to the content accessor.

Rendered in a view as:

<%= render( "my title")) do %>
  Hello, World!
<% end %>


<span title="my title">Hello, World!</span>

Rendering from controllers

It’s also possible to render ViewComponents in controllers:

def show
  render( "My Title")) { "Hello, World!" }

Note: In versions of Rails < 6.1, rendering a ViewComponent from a controller does not include the layout.

Table of contents