Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>EDIT: OK, my first pass on this didn't work because you can't define a value in an initializer that you're later going to pass in from a controller. So you can go about this one of two ways. You can define a <code>CustomFormBuilder</code> class - put it in an initializer - </p> <pre><code>class CustomFormBuilder &lt; ActionView::Helpers::FormBuilder def submit(value, options = {}) @template.hidden_field_tag(options.delete(:custom_param)) + super end end </code></pre> <p>Then pass the <code>:builder</code> option to <code>form_for</code></p> <pre><code>form_for @whatever, builder: CustomFormBuilder </code></pre> <p>and assuming you call <code>submit(value, options)</code> in the form, where options includes your custom_param, it will be overwritten by the custom method that inserts your hidden field with the value you want.</p> <p>The alternative is to monkey patch monkey patch FormTagHelper instead:</p> <pre><code>module ActionView::Helpers::FormTagHelper def extra_tags_for_form_with_custom_param(html_options) hidden_field_tag(html_options.delete('custom_param') + extra_tags_for_form_without_custom_param(html_options) end alias_method_chain :extra_tags_for_form, :custom_param end </code></pre> <p>That's tweaking the code <code>form_for</code> uses to insert the authenticity token at the top of every form. Now you can pass that custom param to <code>form_for</code> after setting it as an instance variable in the controller:</p> <pre><code>form_for @object, custom_param: @custom_param do |f| </code></pre> <hr> <p>If you are using Ruby 2.0+ then you can use module prepend instead of the deprecated alias_method_chain e.g.</p> <pre><code>module CustomParamFormPatch private def extra_tags_for_form(html_options) hidden_field_tag(html_options.delete('custom_param')) + super end end ActionView::Base.prepend(CustomParamFormPatch) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAdding a hidden input field to all the forms in rails
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLuke
    1. USbgates
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI tried specifying the submit_Tag(value, options = {}) . It does not seem to render the hidden input element. I also added a log statement which did not seem to work. I have attached the builder rightly. My forms all use a submit_tag. Anything I'm missing out?
      singulars
      1. PO
      1. USgnarsi
    2. CO`submit_tag` isn't defined on the FormBuilder class, `submit` is. Since `submit_tag` is called on...actually I'm not sure what object those *_tag methods are called on, @template maybe - I don't think you can subclass it. You'd have to monkeypatch `submit_tag` within the FormTagHelper class, which feels more brittle to me. Any reason you're not just using `submit`?
      singulars
      1. PO
      1. USbgates
    3. COI'm not sure why it is not a submit in the first place. I'm now converting it to submit. But is there a way I can access the current controller instance and get the property like in my case? I'm not finding a way to do that.
      singulars
      1. PO
      1. USgnarsi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload