如何在Rails自定义表单构建器中获取name属性及字段生成属性？

Great question! Parsing generated HTML with Nokogiri just to yank out form field attributes is a bit of a workaround—plus it adds unnecessary performance overhead and could break if Rails ever tweaks how it renders form tags under the hood. Luckily, there are much cleaner ways to get those exact attributes (name, value, id, etc.) directly from Rails’ internal form helper system, no HTML parsing required. Let’s walk through two solid approaches:

1. Build Attributes Directly Using FormBuilder’s Built-in Methods #

Rails’ FormBuilder comes with all the tools you need to replicate the attribute logic used by helpers like text_field, without rendering HTML first. Here’s a method that returns a full string of HTML attributes (or a hash, if you prefer) for any given field:

class CustomBuilder < ActionView::Helpers::FormBuilder
  def field_attributes(attribute_name, options = {})
    # Generate the standard Rails field name (e.g., "post[body]" or "comment[post_id]")
    field_name = self.field_name(attribute_name)
    
    # Fetch the field's current value (handles persisted objects, form submissions, and defaults)
    value = options[:value] || object&.send(attribute_name)
    
    # Build core attributes that match what Rails' text_field generates
    attributes = {
      name: field_name,
      id: self.field_id(attribute_name, options),
      value: value,
      type: options[:type] || "text"
    }
    
    # Merge in custom options (like class, placeholder, disabled) while avoiding conflicts
    attributes.merge!(options.except(:type, :value))
    
    # Convert the hash to a properly escaped HTML attribute string
    attributes.map { |key, val| %(#{key}="#{ERB::Util.html_escape(val)}") }.join(" ")
  end
end

How to Use It #

In your view, call this method to populate your input’s attributes:

<%= form_with model: resource, local: true, builder: CustomBuilder do |form| %>
  <input <%= form.field_attributes :body, class: "form-control" %> ref="input">
  <%= form.label :body %>
<% end %>

This approach is fast, maintainable, and uses the same logic as Rails’ native helpers—so it’ll stay in sync with any future Rails updates.

2. Leverage Rails’ Internal Tag Classes #

You mentioned Tag::Base—Rails uses dedicated tag classes (like ActionView::Helpers::Tags::TextField) to handle form field rendering. You can instantiate these classes directly in your builder to get the full set of HTML attributes without touching the rendered HTML. Here’s how:

class CustomBuilder < ActionView::Helpers::FormBuilder
  def tag_attributes(attribute_name, options = {})
    # Initialize the TextField tag class (swap for other types like TextArea or CheckBox as needed)
    tag_instance = ActionView::Helpers::Tags::TextField.new(
      object_name,
      attribute_name,
      self,
      options
    )
    
    # Get the complete HTML attributes hash generated by Rails
    attributes = tag_instance.html_attributes
    
    # Convert to an escaped attribute string for your input tag
    attributes.map { |key, val| %(#{key}="#{ERB::Util.html_escape(val)}") }.join(" ")
  end
end

Why This Works #

The tag class handles all the heavy lifting: it generates the correct nested name attribute, pulls values from the object or form parameters, sets the id with proper naming conventions, and merges your custom options. This is the most Rails-native approach possible without modifying source code.

Bonus: Simplified name Attribute Only #

If you only need the name attribute (like your original tag_name method), skip the extra steps and use FormBuilder’s built-in field_name method directly:

class CustomBuilder < ActionView::Helpers::FormBuilder
  def tag_name(attribute_name)
    %(name="#{self.field_name(attribute_name)}")
  end
end

This is way cleaner than parsing HTML and guarantees you get the exact same name attribute that Rails’ official helpers would generate.

内容的提问来源于stack exchange，提问作者Anonymus