**DO NOT READ THIS FILE ON GITHUB, GUIDES ARE PUBLISHED ON https://guides.rubyonrails.org.** Action View Overview ==================== After reading this guide, you will know: * What Action View is and how to use it with Rails. * How best to use templates, partials, and layouts. * What helpers are provided by Action View. * How to use localized views. -------------------------------------------------------------------------------- What is Action View? -------------------- In Rails, web requests are handled by [Action Controller](action_controller_overview.html) and Action View. Typically, Action Controller is concerned with communicating with the database and performing CRUD actions where necessary. Action View is then responsible for compiling the response. Action View templates are written using embedded Ruby in tags mingled with HTML. To avoid cluttering the templates with boilerplate code, a number of helper classes provide common behavior for forms, dates, and strings. It's also easy to add new helpers to your application as it evolves. NOTE: Some features of Action View are tied to Active Record, but that doesn't mean Action View depends on Active Record. Action View is an independent package that can be used with any sort of Ruby libraries. Using Action View with Rails ---------------------------- For each controller there is an associated directory in the `app/views` directory which holds the template files that make up the views associated with that controller. These files are used to display the view that results from each controller action. Let's take a look at what Rails does by default when creating a new resource using the scaffold generator: ```bash $ rails generate scaffold article [...] invoke scaffold_controller create app/controllers/articles_controller.rb invoke erb create app/views/articles create app/views/articles/index.html.erb create app/views/articles/edit.html.erb create app/views/articles/show.html.erb create app/views/articles/new.html.erb create app/views/articles/_form.html.erb [...] ``` There is a naming convention for views in Rails. Typically, the views share their name with the associated controller action, as you can see above. For example, the index controller action of the `articles_controller.rb` will use the `index.html.erb` view file in the `app/views/articles` directory. The complete HTML returned to the client is composed of a combination of this ERB file, a layout template that wraps it, and all the partials that the view may reference. Within this guide you will find more detailed documentation about each of these three components. Templates, Partials, and Layouts ------------------------------- As mentioned, the final HTML output is a composition of three Rails elements: `Templates`, `Partials` and `Layouts`. Below is a brief overview of each of them. ### Templates Action View templates can be written in several ways. If the template file has a `.erb` extension then it uses a mixture of ERB (Embedded Ruby) and HTML. If the template file has a `.builder` extension then the `Builder::XmlMarkup` library is used. Rails supports multiple template systems and uses a file extension to distinguish amongst them. For example, an HTML file using the ERB template system will have `.html.erb` as a file extension. #### ERB Within an ERB template, Ruby code can be included using both `<% %>` and `<%= %>` tags. The `<% %>` tags are used to execute Ruby code that does not return anything, such as conditions, loops, or blocks, and the `<%= %>` tags are used when you want output. Consider the following loop for names: ```html+erb

Names of all the people

<% @people.each do |person| %> Name: <%= person.name %>
<% end %> ``` The loop is set up using regular embedding tags (`<% %>`) and the name is inserted using the output embedding tags (`<%= %>`). Note that this is not just a usage suggestion: regular output functions such as `print` and `puts` won't be rendered to the view with ERB templates. So this would be wrong: ```html+erb <%# WRONG %> Hi, Mr. <% puts "Frodo" %> ``` To suppress leading and trailing whitespaces, you can use `<%-` `-%>` interchangeably with `<%` and `%>`. #### Builder Builder templates are a more programmatic alternative to ERB. They are especially useful for generating XML content. An XmlMarkup object named `xml` is automatically made available to templates with a `.builder` extension. Here are some basic examples: ```ruby xml.em("emphasized") xml.em { xml.b("emph & bold") } xml.a("A Link", "href" => "https://rubyonrails.org") xml.target("name" => "compile", "option" => "fast") ``` which would produce: ```html emphasized emph & bold A link ``` Any method with a block will be treated as an XML markup tag with nested markup in the block. For example, the following: ```ruby xml.div { xml.h1(@person.name) xml.p(@person.bio) } ``` would produce something like: ```html

David Heinemeier Hansson

A product of Danish Design during the Winter of '79...

``` Below is a full-length RSS example actually used on Basecamp: ```ruby xml.rss("version" => "2.0", "xmlns:dc" => "http://purl.org/dc/elements/1.1/") do xml.channel do xml.title(@feed_title) xml.link(@url) xml.description "Basecamp: Recent items" xml.language "en-us" xml.ttl "40" for item in @recent_items xml.item do xml.title(item_title(item)) xml.description(item_description(item)) if item_description(item) xml.pubDate(item_pubDate(item)) xml.guid(@person.firm.account.url + @recent_items.url(item)) xml.link(@person.firm.account.url + @recent_items.url(item)) xml.tag!("dc:creator", item.author_name) if item_has_creator?(item) end end end end ``` #### Jbuilder [Jbuilder](https://github.com/rails/jbuilder) is a gem that's maintained by the Rails team and included in the default Rails `Gemfile`. It's similar to Builder, but is used to generate JSON, instead of XML. If you don't have it, you can add the following to your `Gemfile`: ```ruby gem 'jbuilder' ``` A Jbuilder object named `json` is automatically made available to templates with a `.jbuilder` extension. Here is a basic example: ```ruby json.name("Alex") json.email("alex@example.com") ``` would produce: ```json { "name": "Alex", "email": "alex@example.com" } ``` See the [Jbuilder documentation](https://github.com/rails/jbuilder#jbuilder) for more examples and information. #### Template Caching By default, Rails will compile each template to a method in order to render it. When you alter a template, Rails will check the file's modification time and recompile it in development mode. ### Partials Partial templates - usually just called "partials" - are another device for breaking the rendering process into more manageable chunks. With partials, you can extract pieces of code from your templates to separate files and also reuse them throughout your templates. #### Naming Partials To render a partial as part of a view, you use the `render` method within the view: ```erb <%= render "menu" %> ``` This will render a file named `_menu.html.erb` at that point within the view that is being rendered. Note the leading underscore character: partials are named with a leading underscore to distinguish them from regular views, even though they are referred to without the underscore. This holds true even when you're pulling in a partial from another folder: ```erb <%= render "shared/menu" %> ``` That code will pull in the partial from `app/views/shared/_menu.html.erb`. #### Using Partials to simplify Views One way to use partials is to treat them as the equivalent of subroutines; a way to move details out of a view so that you can grasp what's going on more easily. For example, you might have a view that looks like this: ```html+erb <%= render "shared/ad_banner" %>

Products

Here are a few of our fine products:

<% @products.each do |product| %> <%= render partial: "product", locals: { product: product } %> <% end %> <%= render "shared/footer" %> ``` Here, the `_ad_banner.html.erb` and `_footer.html.erb` partials could contain content that is shared among many pages in your application. You don't need to see the details of these sections when you're concentrating on a particular page. #### `render` without `partial` and `locals` options In the above example, `render` takes 2 options: `partial` and `locals`. But if these are the only options you want to pass, you can skip using these options. For example, instead of: ```erb <%= render partial: "product", locals: { product: @product } %> ``` You can also do: ```erb <%= render "product", product: @product %> ``` #### The `as` and `object` options By default `ActionView::Partials::PartialRenderer` has its object in a local variable with the same name as the template. So, given: ```erb <%= render partial: "product" %> ``` within `_product` partial we'll get `@product` in the local variable `product`, as if we had written: ```erb <%= render partial: "product", locals: { product: @product } %> ``` The `object` option can be used to directly specify which object is rendered into the partial; useful when the template's object is elsewhere (e.g. in a different instance variable or in a local variable). For example, instead of: ```erb <%= render partial: "product", locals: { product: @item } %> ``` we would do: ```erb <%= render partial: "product", object: @item %> ``` With the `as` option we can specify a different name for the said local variable. For example, if we wanted it to be `item` instead of `product` we would do: ```erb <%= render partial: "product", object: @item, as: "item" %> ``` This is equivalent to ```erb <%= render partial: "product", locals: { item: @item } %> ``` #### Rendering Collections It is very common that a template will need to iterate over a collection and render a sub-template for each of the elements. This pattern has been implemented as a single method that accepts an array and renders a partial for each one of the elements in the array. So this example for rendering all the products: ```erb <% @products.each do |product| %> <%= render partial: "product", locals: { product: product } %> <% end %> ``` can be rewritten in a single line: ```erb <%= render partial: "product", collection: @products %> ``` When a partial is called with a collection, the individual instances of the partial have access to the member of the collection being rendered via a variable named after the partial. In this case, the partial is `_product`, and within it you can refer to `product` to get the collection member that is being rendered. You can use a shorthand syntax for rendering collections. Assuming `@products` is a collection of `Product` instances, you can simply write the following to produce the same result: ```erb <%= render @products %> ``` Rails determines the name of the partial to use by looking at the model name in the collection, `Product` in this case. In fact, you can even render a collection made up of instances of different models using this shorthand, and Rails will choose the proper partial for each member of the collection. #### Spacer Templates You can also specify a second partial to be rendered between instances of the main partial by using the `:spacer_template` option: ```erb <%= render partial: @products, spacer_template: "product_ruler" %> ``` Rails will render the `_product_ruler` partial (with no data passed to it) between each pair of `_product` partials. ### Layouts Layouts can be used to render a common view template around the results of Rails controller actions. Typically, a Rails application will have a couple of layouts that pages will be rendered within. For example, a site might have one layout for a logged in user and another for the marketing or sales side of the site. The logged in user layout might include top-level navigation that should be present across many controller actions. The sales layout for a SaaS app might include top-level navigation for things like "Pricing" and "Contact Us" pages. You would expect each layout to have a different look and feel. You can read about layouts in more detail in the [Layouts and Rendering in Rails](layouts_and_rendering.html) guide. Partial Layouts --------------- Partials can have their own layouts applied to them. These layouts are different from those applied to a controller action, but they work in a similar fashion. Let's say we're displaying an article on a page which should be wrapped in a `div` for display purposes. Firstly, we'll create a new `Article`: ```ruby Article.create(body: 'Partial Layouts are cool!') ``` In the `show` template, we'll render the `_article` partial wrapped in the `box` layout: **articles/show.html.erb** ```erb <%= render partial: 'article', layout: 'box', locals: { article: @article } %> ``` The `box` layout simply wraps the `_article` partial in a `div`: **articles/_box.html.erb** ```html+erb
<%= yield %>
``` Note that the partial layout has access to the local `article` variable that was passed into the `render` call. However, unlike application-wide layouts, partial layouts still have the underscore prefix. You can also render a block of code within a partial layout instead of calling `yield`. For example, if we didn't have the `_article` partial, we could do this instead: **articles/show.html.erb** ```html+erb <% render(layout: 'box', locals: { article: @article }) do %>

<%= article.body %>

<% end %> ``` Supposing we use the same `_box` partial from above, this would produce the same output as the previous example. View Paths ---------- When rendering a response, the controller needs to resolve where the different views are located. By default it only looks inside the `app/views` directory. We can add other locations and give them a certain precedence when resolving paths using the `prepend_view_path` and `append_view_path` methods. ### Prepend view path This can be helpful for example, when we want to put views inside a different directory for subdomains. We can do this by using: ```ruby prepend_view_path "app/views/#{request.subdomain}" ``` Then Action View will look first in this directory when resolving views. ### Append view path Similarly, we can append paths: ```ruby append_view_path "app/views/direct" ``` This will add `app/views/direct` to the end of the lookup paths. Overview of helpers provided by Action View ------------------------------------------- WIP: Not all the helpers are listed here. For a full list see the [API documentation](https://api.rubyonrails.org/classes/ActionView/Helpers.html) The following is only a brief overview summary of the helpers available in Action View. It's recommended that you review the [API Documentation](https://api.rubyonrails.org/classes/ActionView/Helpers.html), which covers all of the helpers in more detail, but this should serve as a good starting point. ### AssetTagHelper This module provides methods for generating HTML that links views to assets such as images, JavaScript files, stylesheets, and feeds. By default, Rails links to these assets on the current host in the public folder, but you can direct Rails to link to assets from a dedicated assets server by setting `config.action_controller.asset_host` in the application configuration, typically in `config/environments/production.rb`. For example, let's say your asset host is `assets.example.com`: ```ruby config.action_controller.asset_host = "assets.example.com" image_tag("rails.png") # => ``` #### auto_discovery_link_tag Returns a link tag that browsers and feed readers can use to auto-detect an RSS, Atom, or JSON feed. ```ruby auto_discovery_link_tag(:rss, "http://www.example.com/feed.rss", { title: "RSS Feed" }) # => ``` #### image_path Computes the path to an image asset in the `app/assets/images` directory. Full paths from the document root will be passed through. Used internally by `image_tag` to build the image path. ```ruby image_path("edit.png") # => /assets/edit.png ``` Fingerprint will be added to the filename if config.assets.digest is set to true. ```ruby image_path("edit.png") # => /assets/edit-2d1a2db63fc738690021fedb5a65b68e.png ``` #### image_url Computes the URL to an image asset in the `app/assets/images` directory. This will call `image_path` internally and merge with your current host or your asset host. ```ruby image_url("edit.png") # => http://www.example.com/assets/edit.png ``` #### image_tag Returns an HTML image tag for the source. The source can be a full path or a file that exists in your `app/assets/images` directory. ```ruby image_tag("icon.png") # => ``` #### javascript_include_tag Returns an HTML script tag for each of the sources provided. You can pass in the filename (`.js` extension is optional) of JavaScript files that exist in your `app/assets/javascripts` directory for inclusion into the current page or you can pass the full path relative to your document root. ```ruby javascript_include_tag "common" # => ``` #### javascript_path Computes the path to a JavaScript asset in the `app/assets/javascripts` directory. If the source filename has no extension, `.js` will be appended. Full paths from the document root will be passed through. Used internally by `javascript_include_tag` to build the script path. ```ruby javascript_path "common" # => /assets/common.js ``` #### javascript_url Computes the URL to a JavaScript asset in the `app/assets/javascripts` directory. This will call `javascript_path` internally and merge with your current host or your asset host. ```ruby javascript_url "common" # => http://www.example.com/assets/common.js ``` #### stylesheet_link_tag Returns a stylesheet link tag for the sources specified as arguments. If you don't specify an extension, `.css` will be appended automatically. ```ruby stylesheet_link_tag "application" # => ``` #### stylesheet_path Computes the path to a stylesheet asset in the `app/assets/stylesheets` directory. If the source filename has no extension, `.css` will be appended. Full paths from the document root will be passed through. Used internally by `stylesheet_link_tag` to build the stylesheet path. ```ruby stylesheet_path "application" # => /assets/application.css ``` #### stylesheet_url Computes the URL to a stylesheet asset in the `app/assets/stylesheets` directory. This will call `stylesheet_path` internally and merge with your current host or your asset host. ```ruby stylesheet_url "application" # => http://www.example.com/assets/application.css ``` ### AtomFeedHelper #### atom_feed This helper makes building an Atom feed easy. Here's a full usage example: **config/routes.rb** ```ruby resources :articles ``` **app/controllers/articles_controller.rb** ```ruby def index @articles = Article.all respond_to do |format| format.html format.atom end end ``` **app/views/articles/index.atom.builder** ```ruby atom_feed do |feed| feed.title("Articles Index") feed.updated(@articles.first.created_at) @articles.each do |article| feed.entry(article) do |entry| entry.title(article.title) entry.content(article.body, type: 'html') entry.author do |author| author.name(article.author_name) end end end end ``` ### BenchmarkHelper #### benchmark Allows you to measure the execution time of a block in a template and records the result to the log. Wrap this block around expensive operations or possible bottlenecks to get a time reading for the operation. ```html+erb <% benchmark "Process data files" do %> <%= expensive_files_operation %> <% end %> ``` This would add something like "Process data files (0.34523)" to the log, which you can then use to compare timings when optimizing your code. ### CacheHelper #### cache A method for caching fragments of a view rather than an entire action or page. This technique is useful for caching pieces like menus, lists of news topics, static HTML fragments, and so on. This method takes a block that contains the content you wish to cache. See `AbstractController::Caching::Fragments` for more information. ```erb <% cache do %> <%= render "shared/footer" %> <% end %> ``` ### CaptureHelper #### capture The `capture` method allows you to extract part of a template into a variable. You can then use this variable anywhere in your templates or layout. ```html+erb <% @greeting = capture do %>

Welcome! The date and time is <%= Time.now %>

<% end %> ``` The captured variable can then be used anywhere else. ```html+erb Welcome! <%= @greeting %> ``` #### content_for Calling `content_for` stores a block of markup in an identifier for later use. You can make subsequent calls to the stored content in other templates or the layout by passing the identifier as an argument to `yield`. For example, let's say we have a standard application layout, but also a special page that requires certain JavaScript that the rest of the site doesn't need. We can use `content_for` to include this JavaScript on our special page without fattening up the rest of the site. **app/views/layouts/application.html.erb** ```html+erb Welcome! <%= yield :special_script %>

Welcome! The date and time is <%= Time.now %>

``` **app/views/articles/special.html.erb** ```html+erb

This is a special page.

<% content_for :special_script do %> <% end %> ``` ### DateHelper #### date_select Returns a set of select tags (one for year, month, and day) pre-selected for accessing a specified date-based attribute. ```ruby date_select("article", "published_on") ``` #### datetime_select Returns a set of select tags (one for year, month, day, hour, and minute) pre-selected for accessing a specified datetime-based attribute. ```ruby datetime_select("article", "published_on") ``` #### distance_of_time_in_words Reports the approximate distance in time between two Time or Date objects or integers as seconds. Set `include_seconds` to true if you want more detailed approximations. ```ruby distance_of_time_in_words(Time.now, Time.now + 15.seconds) # => less than a minute distance_of_time_in_words(Time.now, Time.now + 15.seconds, include_seconds: true) # => less than 20 seconds ``` #### select_date Returns a set of HTML select-tags (one for year, month, and day) pre-selected with the `date` provided. ```ruby # Generates a date select that defaults to the date provided (six days after today) select_date(Time.today + 6.days) # Generates a date select that defaults to today (no specified date) select_date() ``` #### select_datetime Returns a set of HTML select-tags (one for year, month, day, hour, and minute) pre-selected with the `datetime` provided. ```ruby # Generates a datetime select that defaults to the datetime provided (four days after today) select_datetime(Time.now + 4.days) # Generates a datetime select that defaults to today (no specified datetime) select_datetime() ``` #### select_day Returns a select tag with options for each of the days 1 through 31 with the current day selected. ```ruby # Generates a select field for days that defaults to the day for the date provided select_day(Time.today + 2.days) # Generates a select field for days that defaults to the number given select_day(5) ``` #### select_hour Returns a select tag with options for each of the hours 0 through 23 with the current hour selected. ```ruby # Generates a select field for hours that defaults to the hours for the time provided select_hour(Time.now + 6.hours) ``` #### select_minute Returns a select tag with options for each of the minutes 0 through 59 with the current minute selected. ```ruby # Generates a select field for minutes that defaults to the minutes for the time provided. select_minute(Time.now + 10.minutes) ``` #### select_month Returns a select tag with options for each of the months January through December with the current month selected. ```ruby # Generates a select field for months that defaults to the current month select_month(Date.today) ``` #### select_second Returns a select tag with options for each of the seconds 0 through 59 with the current second selected. ```ruby # Generates a select field for seconds that defaults to the seconds for the time provided select_second(Time.now + 16.seconds) ``` #### select_time Returns a set of HTML select-tags (one for hour and minute). ```ruby # Generates a time select that defaults to the time provided select_time(Time.now) ``` #### select_year Returns a select tag with options for each of the five years on each side of the current, which is selected. The five year radius can be changed using the `:start_year` and `:end_year` keys in the `options`. ```ruby # Generates a select field for five years on either side of Date.today that defaults to the current year select_year(Date.today) # Generates a select field from 1900 to 2009 that defaults to the current year select_year(Date.today, start_year: 1900, end_year: 2009) ``` #### time_ago_in_words Like `distance_of_time_in_words`, but where `to_time` is fixed to `Time.now`. ```ruby time_ago_in_words(3.minutes.from_now) # => 3 minutes ``` #### time_select Returns a set of select tags (one for hour, minute, and optionally second) pre-selected for accessing a specified time-based attribute. The selects are prepared for multi-parameter assignment to an Active Record object. ```ruby # Creates a time select tag that, when POSTed, will be stored in the order variable in the submitted attribute time_select("order", "submitted") ``` ### DebugHelper Returns a `pre` tag that has object dumped by YAML. This creates a very readable way to inspect an object. ```ruby my_hash = { 'first' => 1, 'second' => 'two', 'third' => [1,2,3] } debug(my_hash) ``` ```html
---
first: 1
second: two
third:
- 1
- 2
- 3
``` ### FormHelper Form helpers are designed to make working with models much easier compared to using just standard HTML elements by providing a set of methods for creating forms based on your models. This helper generates the HTML for forms, providing a method for each sort of input (e.g., text, password, select, and so on). When the form is submitted (i.e., when the user hits the submit button or form.submit is called via JavaScript), the form inputs will be bundled into the params object and passed back to the controller. There are two types of form helpers: those that specifically work with model attributes and those that don't. This helper deals with those that work with model attributes; to see an example of form helpers that don't work with model attributes, check the `ActionView::Helpers::FormTagHelper` documentation. The core method of this helper, `form_for`, gives you the ability to create a form for a model instance; for example, let's say that you have a model Person and want to create a new instance of it: ```html+erb # Note: a @person variable will have been created in the controller (e.g. @person = Person.new) <%= form_for @person, url: { action: "create" } do |f| %> <%= f.text_field :first_name %> <%= f.text_field :last_name %> <%= submit_tag 'Create' %> <% end %> ``` The HTML generated for this would be: ```html
``` The params object created when this form is submitted would look like: ```ruby {"utf8" => "✓", "authenticity_token" => "lTuvBzs7ANygT0NFinXj98tfw3Emfm65wwYLbUvoWsK2pngccIQSUorM2C035M9dZswXgWTvKwFS8W5TVblpYw==", "person" => {"first_name" => "William", "last_name" => "Smith"}, "commit" => "Create", "controller" => "people", "action" => "create"} ``` The params hash has a nested person value, which can therefore be accessed with `params[:person]` in the controller. #### check_box Returns a checkbox tag tailored for accessing a specified attribute. ```ruby # Let's say that @article.validated? is 1: check_box("article", "validated") # => # ``` #### fields_for Creates a scope around a specific model object like `form_for`, but doesn't create the form tags themselves. This makes `fields_for` suitable for specifying additional model objects in the same form: ```html+erb <%= form_for @person, url: { action: "update" } do |person_form| %> First name: <%= person_form.text_field :first_name %> Last name : <%= person_form.text_field :last_name %> <%= fields_for @person.permission do |permission_fields| %> Admin? : <%= permission_fields.check_box :admin %> <% end %> <% end %> ``` #### file_field Returns a file upload input tag tailored for accessing a specified attribute. ```ruby file_field(:user, :avatar) # => ``` #### form_for Creates a form and a scope around a specific model object that is used as a base for questioning about values for the fields. ```html+erb <%= form_for @article do |f| %> <%= f.label :title, 'Title' %>: <%= f.text_field :title %>
<%= f.label :body, 'Body' %>: <%= f.text_area :body %>
<% end %> ``` #### hidden_field Returns a hidden input tag tailored for accessing a specified attribute. ```ruby hidden_field(:user, :token) # => ``` #### label Returns a label tag tailored for labelling an input field for a specified attribute. ```ruby label(:article, :title) # => ``` #### password_field Returns an input tag of the "password" type tailored for accessing a specified attribute. ```ruby password_field(:login, :pass) # => ``` #### radio_button Returns a radio button tag for accessing a specified attribute. ```ruby # Let's say that @article.category returns "rails": radio_button("article", "category", "rails") radio_button("article", "category", "java") # => # ``` #### text_area Returns a textarea opening and closing tag set tailored for accessing a specified attribute. ```ruby text_area(:comment, :text, size: "20x30") # => ``` #### text_field Returns an input tag of the "text" type tailored for accessing a specified attribute. ```ruby text_field(:article, :title) # => ``` #### email_field Returns an input tag of the "email" type tailored for accessing a specified attribute. ```ruby email_field(:user, :email) # => ``` #### url_field Returns an input tag of the "url" type tailored for accessing a specified attribute. ```ruby url_field(:user, :url) # => ``` ### FormOptionsHelper Provides a number of methods for turning different kinds of containers into a set of option tags. #### collection_select Returns `select` and `option` tags for the collection of existing return values of `method` for `object`'s class. Example object structure for use with this method: ```ruby class Article < ApplicationRecord belongs_to :author end class Author < ApplicationRecord has_many :articles def name_with_initial "#{first_name.first}. #{last_name}" end end ``` Sample usage (selecting the associated Author for an instance of Article, `@article`): ```ruby collection_select(:article, :author_id, Author.all, :id, :name_with_initial, { prompt: true }) ``` If `@article.author_id` is 1, this would return: ```html ``` #### collection_radio_buttons Returns `radio_button` tags for the collection of existing return values of `method` for `object`'s class. Example object structure for use with this method: ```ruby class Article < ApplicationRecord belongs_to :author end class Author < ApplicationRecord has_many :articles def name_with_initial "#{first_name.first}. #{last_name}" end end ``` Sample usage (selecting the associated Author for an instance of Article, `@article`): ```ruby collection_radio_buttons(:article, :author_id, Author.all, :id, :name_with_initial) ``` If `@article.author_id` is 1, this would return: ```html ``` Recovering some option passed (e.g. programatically checking an object from collection): ```ruby collection_radio_buttons(:article, :author_id, Author.all, :id, :name_with_initial, {checked: Author.last}) ``` In this case, the last object from the collection will be checked: ```html ``` To access the passed options programatically (e.g. adding a custom class if checked): **Sample html.erb** ```html+erb <%= collection_radio_buttons(:article, :author_id, Author.all, :id, :name_with_initial, {checked: Author.last, required: true} do |rb| %> <%= rb.label(class: "#{'my-custom-class' if rb.value == Author.last.id}") { rb.radio_button + rb.text } %> <% end %> ``` #### collection_check_boxes Returns `check_box` tags for the collection of existing return values of `method` for `object`'s class. Example object structure for use with this method: ```ruby class Article < ApplicationRecord has_and_belongs_to_many :authors end class Author < ApplicationRecord has_and_belongs_to_many :articles def name_with_initial "#{first_name.first}. #{last_name}" end end ``` Sample usage (selecting the associated Authors for an instance of Article, `@article`): ```ruby collection_check_boxes(:article, :author_ids, Author.all, :id, :name_with_initial) ``` If `@article.author_ids` is [1], this would return: ```html ``` #### option_groups_from_collection_for_select Returns a string of `option` tags, like `options_from_collection_for_select`, but groups them by `optgroup` tags based on the object relationships of the arguments. Example object structure for use with this method: ```ruby class Continent < ApplicationRecord has_many :countries # attribs: id, name end class Country < ApplicationRecord belongs_to :continent # attribs: id, name, continent_id end ``` Sample usage: ```ruby option_groups_from_collection_for_select(@continents, :countries, :name, :id, :name, 3) ``` Possible output: ```html ... ... ``` NOTE: Only the `optgroup` and `option` tags are returned, so you still have to wrap the output in an appropriate `select` tag. #### options_for_select Accepts a container (hash, array, enumerable, your type) and returns a string of option tags. ```ruby options_for_select([ "VISA", "MasterCard" ]) # => ``` NOTE: Only the `option` tags are returned, you have to wrap this call in a regular HTML `select` tag. #### options_from_collection_for_select Returns a string of option tags that have been compiled by iterating over the `collection` and assigning the result of a call to the `value_method` as the option value and the `text_method` as the option text. ```ruby # options_from_collection_for_select(collection, value_method, text_method, selected = nil) ``` For example, imagine a loop iterating over each person in `@project.people` to generate an input tag: ```ruby options_from_collection_for_select(@project.people, "id", "name") # => ``` NOTE: Only the `option` tags are returned, you have to wrap this call in a regular HTML `select` tag. #### select Create a select tag and a series of contained option tags for the provided object and method. Example: ```ruby select("article", "person_id", Person.all.collect { |p| [ p.name, p.id ] }, { include_blank: true }) ``` If `@article.person_id` is 1, this would become: ```html ``` #### time_zone_options_for_select Returns a string of option tags for pretty much any time zone in the world. #### time_zone_select Returns select and option tags for the given object and method, using `time_zone_options_for_select` to generate the list of option tags. ```ruby time_zone_select("user", "time_zone") ``` #### date_field Returns an input tag of the "date" type tailored for accessing a specified attribute. ```ruby date_field("user", "dob") ``` ### FormTagHelper Provides a number of methods for creating form tags that don't rely on an Active Record object assigned to the template like FormHelper does. Instead, you provide the names and values manually. #### check_box_tag Creates a check box form input tag. ```ruby check_box_tag 'accept' # => ``` #### field_set_tag Creates a field set for grouping HTML form elements. ```html+erb <%= field_set_tag do %>

<%= text_field_tag 'name' %>

<% end %> # =>

``` #### file_field_tag Creates a file upload field. ```html+erb <%= form_tag({ action: "post" }, multipart: true) do %> <%= file_field_tag "file" %> <%= submit_tag %> <% end %> ``` Example output: ```ruby file_field_tag 'attachment' # => ``` #### form_tag Starts a form tag that points the action to a URL configured with `url_for_options` just like `ActionController::Base#url_for`. ```html+erb <%= form_tag '/articles' do %>
<%= submit_tag 'Save' %>
<% end %> # =>
``` #### hidden_field_tag Creates a hidden form input field used to transmit data that would be lost due to HTTP's statelessness or data that should be hidden from the user. ```ruby hidden_field_tag 'token', 'VUBJKB23UIVI1UU1VOBVI@' # => ``` #### image_submit_tag Displays an image which when clicked will submit the form. ```ruby image_submit_tag("login.png") # => ``` #### label_tag Creates a label field. ```ruby label_tag 'name' # => ``` #### password_field_tag Creates a password field, a masked text field that will hide the users input behind a mask character. ```ruby password_field_tag 'pass' # => ``` #### radio_button_tag Creates a radio button; use groups of radio buttons named the same to allow users to select from a group of options. ```ruby radio_button_tag 'favorite_color', 'maroon' # => ``` #### select_tag Creates a dropdown selection box. ```ruby select_tag "people", "" # => ``` #### submit_tag Creates a submit button with the text provided as the caption. ```ruby submit_tag "Publish this article" # => ``` #### text_area_tag Creates a text input area; use a textarea for longer text inputs such as blog posts or descriptions. ```ruby text_area_tag 'article' # => ``` #### text_field_tag Creates a standard text field; use these text fields to input smaller chunks of text like a username or a search query. ```ruby text_field_tag 'name' # => ``` #### email_field_tag Creates a standard input field of email type. ```ruby email_field_tag 'email' # => ``` #### url_field_tag Creates a standard input field of url type. ```ruby url_field_tag 'url' # => ``` #### date_field_tag Creates a standard input field of date type. ```ruby date_field_tag "dob" # => ``` ### JavaScriptHelper Provides functionality for working with JavaScript in your views. #### escape_javascript Escape carrier returns and single and double quotes for JavaScript segments. #### javascript_tag Returns a JavaScript tag wrapping the provided code. ```ruby javascript_tag "alert('All is good')" ``` ```html ``` ### NumberHelper Provides methods for converting numbers into formatted strings. Methods are provided for phone numbers, currency, percentage, precision, positional notation, and file size. #### number_to_currency Formats a number into a currency string (e.g., $13.65). ```ruby number_to_currency(1234567890.50) # => $1,234,567,890.50 ``` #### number_to_human_size Formats the bytes in size into a more understandable representation; useful for reporting file sizes to users. ```ruby number_to_human_size(1234) # => 1.2 KB number_to_human_size(1234567) # => 1.2 MB ``` #### number_to_percentage Formats a number as a percentage string. ```ruby number_to_percentage(100, precision: 0) # => 100% ``` #### number_to_phone Formats a number into a phone number (US by default). ```ruby number_to_phone(1235551234) # => 123-555-1234 ``` #### number_with_delimiter Formats a number with grouped thousands using a delimiter. ```ruby number_with_delimiter(12345678) # => 12,345,678 ``` #### number_with_precision Formats a number with the specified level of `precision`, which defaults to 3. ```ruby number_with_precision(111.2345) # => 111.235 number_with_precision(111.2345, precision: 2) # => 111.23 ``` ### SanitizeHelper The SanitizeHelper module provides a set of methods for scrubbing text of undesired HTML elements. #### sanitize This sanitize helper will HTML encode all tags and strip all attributes that aren't specifically allowed. ```ruby sanitize @article.body ``` If either the `:attributes` or `:tags` options are passed, only the mentioned attributes and tags are allowed and nothing else. ```ruby sanitize @article.body, tags: %w(table tr td), attributes: %w(id class style) ``` To change defaults for multiple uses, for example adding table tags to the default: ```ruby class Application < Rails::Application config.action_view.sanitized_allowed_tags = 'table', 'tr', 'td' end ``` #### sanitize_css(style) Sanitizes a block of CSS code. #### strip_links(html) Strips all link tags from text leaving just the link text. ```ruby strip_links('Ruby on Rails') # => Ruby on Rails ``` ```ruby strip_links('emails to me@email.com.') # => emails to me@email.com. ``` ```ruby strip_links('Blog: Visit.') # => Blog: Visit. ``` #### strip_tags(html) Strips all HTML tags from the html, including comments. This functionality is powered by the rails-html-sanitizer gem. ```ruby strip_tags("Strip these tags!") # => Strip these tags! ``` ```ruby strip_tags("Bold no more! See more") # => Bold no more! See more ``` NB: The output may still contain unescaped '<', '>', '&' characters and confuse browsers. ### CsrfHelper Returns meta tags "csrf-param" and "csrf-token" with the name of the cross-site request forgery protection parameter and token, respectively. ```html <%= csrf_meta_tags %> ``` NOTE: Regular forms generate hidden fields so they do not use these tags. More details can be found in the [Rails Security Guide](security.html#cross-site-request-forgery-csrf). Localized Views --------------- Action View has the ability to render different templates depending on the current locale. For example, suppose you have an `ArticlesController` with a show action. By default, calling this action will render `app/views/articles/show.html.erb`. But if you set `I18n.locale = :de`, then `app/views/articles/show.de.html.erb` will be rendered instead. If the localized template isn't present, the undecorated version will be used. This means you're not required to provide localized views for all cases, but they will be preferred and used if available. You can use the same technique to localize the rescue files in your public directory. For example, setting `I18n.locale = :de` and creating `public/500.de.html` and `public/404.de.html` would allow you to have localized rescue pages. Since Rails doesn't restrict the symbols that you use to set I18n.locale, you can leverage this system to display different content depending on anything you like. For example, suppose you have some "expert" users that should see different pages from "normal" users. You could add the following to `app/controllers/application.rb`: ```ruby before_action :set_expert_locale def set_expert_locale I18n.locale = :expert if current_user.expert? end ``` Then you could create special views like `app/views/articles/show.expert.html.erb` that would only be displayed to expert users. You can read more about the Rails Internationalization (I18n) API [here](i18n.html).