<?xml version="1.0" encoding="UTF-8"?>
<ticket>
  <assigned-user-id type="integer">22033</assigned-user-id>
  <attachments-count type="integer">0</attachments-count>
  <closed type="boolean">true</closed>
  <created-at type="datetime">2009-08-05T08:34:09-04:00</created-at>
  <creator-id type="integer">65234</creator-id>
  <milestone-due-on type="datetime" nil="true"></milestone-due-on>
  <milestone-id type="integer" nil="true"></milestone-id>
  <number type="integer">112</number>
  <permalink>attribute-with-multiple-parameters</permalink>
  <priority type="integer">37090</priority>
  <project-id type="integer">16601</project-id>
  <raw-data type="binary" nil="true" encoding="base64"></raw-data>
  <state>moved_to_github</state>
  <tag nil="true"></tag>
  <title>Attribute with multiple parameters</title>
  <updated-at type="datetime">2009-08-07T18:30:04-04:00</updated-at>
  <user-id type="integer">22033</user-id>
  <user-name>Ben Johnson</user-name>
  <creator-name>Jean-Hadrien Chabran</creator-name>
  <assigned-user-name>Ben Johnson</assigned-user-name>
  <url>http://binarylogic.lighthouseapp.com/projects/16601/tickets/112</url>
  <original-body>Hello, here is a feature 

Using named scope like &quot;created_at_after&quot; with helper like &quot;form.date_select&quot; which produces created_at(1i), created_at(2i) ... are not handled.

@@@ html
&lt;% form_for(@foos) do |f| %&gt;
    &lt;p&gt;
      &lt;%= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%= f.date_select :bar_at_after %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%#= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%#= f.text_field :bar_at %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%= f.label :bar %&gt;
      &lt;%= f.text_field :bar_equals %&gt;
    &lt;/p&gt;
    
    &lt;p&gt;
      &lt;%= f.submit :search %&gt;
    &lt;/p&gt;
@@@

It ends in an obvious attribute(xi) not recognized. I can still used a text_field helper and pass a string as shown in the example, but that's not always what can be expected in a search form. 

I feel it's would be a nice feature to have. 

JH. Chabran</original-body>
  <latest-body>Hello, here is a feature 

Using named scope like &quot;created_at_after&quot; with helper like &quot;form.date_select&quot; which produces created_at(1i), created_at(2i) ... are not handled.

@@@ html
&lt;% form_for(@foos) do |f| %&gt;
    &lt;p&gt;
      &lt;%= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%= f.date_select :bar_at_after %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%#= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%#= f.text_field :bar_at %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%= f.label :bar %&gt;
      &lt;%= f.text_field :bar_equals %&gt;
    &lt;/p&gt;
    
    &lt;p&gt;
      &lt;%= f.submit :search %&gt;
    &lt;/p&gt;
@@@

It ends in an obvious attribute(xi) not recognized. I can still used a text_field helper and pass a string as shown in the example, but that's not always what can be expected in a search form. 

I feel it's would be a nice feature to have. 

JH. Chabran</latest-body>
  <original-body-html>&lt;div&gt;&lt;p&gt;Hello, here is a feature&lt;/p&gt;
&lt;p&gt;Using named scope like &quot;created_at_after&quot; with helper like
&quot;form.date_select&quot; which produces created_at(1i), created_at(2i)
... are not handled.&lt;/p&gt;


&lt;pre&gt;&lt;code class=&quot;html&quot;&gt;
&amp;lt;% form_for(@foos) do |f| %&amp;gt;
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.label :bar_at, 'Bar at after' %&amp;gt;
      &amp;lt;%= f.date_select :bar_at_after %&amp;gt;
    &amp;lt;/p&amp;gt;
  
    &amp;lt;p&amp;gt;
      &amp;lt;%#= f.label :bar_at, 'Bar at after' %&amp;gt;
      &amp;lt;%#= f.text_field :bar_at %&amp;gt;
    &amp;lt;/p&amp;gt;
  
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.label :bar %&amp;gt;
      &amp;lt;%= f.text_field :bar_equals %&amp;gt;
    &amp;lt;/p&amp;gt;
    
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.submit :search %&amp;gt;
    &amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It ends in an obvious attribute(xi) not recognized. I can still
used a text_field helper and pass a string as shown in the example,
but that's not always what can be expected in a search form.&lt;/p&gt;
&lt;p&gt;I feel it's would be a nice feature to have.&lt;/p&gt;
&lt;p&gt;JH. Chabran&lt;/p&gt;&lt;/div&gt;</original-body-html>
  <versions type="array">
    <version type="Ticket::Version">
      <assigned-user-id type="integer">22033</assigned-user-id>
      <attachments-count type="integer">0</attachments-count>
      <body>Hello, here is a feature request

Using named scope like &quot;created_at_after&quot; with helper like &quot;form.date_select&quot; which produces created_at(1i), created_at(2i) ... are not handled.

@@@ html
&lt;% form_for(@foos) do |f| %&gt;
    &lt;p&gt;
      &lt;%= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%= f.date_select :bar_at_after %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%#= f.label :bar_at, 'Bar at after' %&gt;
      &lt;%#= f.text_field :bar_at %&gt;
    &lt;/p&gt;
  
    &lt;p&gt;
      &lt;%= f.label :bar %&gt;
      &lt;%= f.text_field :bar_equals %&gt;
    &lt;/p&gt;
    
    &lt;p&gt;
      &lt;%= f.submit :search %&gt;
    &lt;/p&gt;
@@@

It ends in an obvious attribute(xi) not recognized. I can still used a text_field helper and pass a string as shown in the example, but that's not always what can be expected in a search form. 

It would be nice feature to have.

JH. Chabran</body>
      <body-html>&lt;div&gt;&lt;p&gt;Hello, here is a feature request&lt;/p&gt;
&lt;p&gt;Using named scope like &quot;created_at_after&quot; with helper like
&quot;form.date_select&quot; which produces created_at(1i), created_at(2i)
... are not handled.&lt;/p&gt;
&lt;pre&gt;
&lt;code class=&quot;html&quot;&gt;&amp;lt;% form_for(@foos) do |f| %&amp;gt;
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.label :bar_at, 'Bar at after' %&amp;gt;
      &amp;lt;%= f.date_select :bar_at_after %&amp;gt;
    &amp;lt;/p&amp;gt;
  
    &amp;lt;p&amp;gt;
      &amp;lt;%#= f.label :bar_at, 'Bar at after' %&amp;gt;
      &amp;lt;%#= f.text_field :bar_at %&amp;gt;
    &amp;lt;/p&amp;gt;
  
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.label :bar %&amp;gt;
      &amp;lt;%= f.text_field :bar_equals %&amp;gt;
    &amp;lt;/p&amp;gt;
    
    &amp;lt;p&amp;gt;
      &amp;lt;%= f.submit :search %&amp;gt;
    &amp;lt;/p&amp;gt;&lt;/code&gt;
&lt;/pre&gt;
&lt;p&gt;It ends in an obvious attribute(xi) not recognized. I can still
used a text_field helper and pass a string as shown in the example,
but that's not always what can be expected in a search form.&lt;/p&gt;
&lt;p&gt;It would be nice feature to have.&lt;/p&gt;
&lt;p&gt;JH. Chabran&lt;/p&gt;&lt;/div&gt;</body-html>
      <closed type="boolean">false</closed>
      <created-at type="datetime">2009-08-05T08:34:09-04:00</created-at>
      <creator-id type="integer">65234</creator-id>
      <diffable-attributes type="yaml">--- {}

</diffable-attributes>
      <milestone-id type="integer" nil="true"></milestone-id>
      <number type="integer">112</number>
      <permalink>attribute-with-multiple-parameters</permalink>
      <priority type="integer">0</priority>
      <project-id type="integer">16601</project-id>
      <state>new</state>
      <tag nil="true"></tag>
      <title>Attribute with multiple parameters</title>
      <updated-at type="datetime">2009-08-06T18:25:14-04:00</updated-at>
      <user-id type="integer">65234</user-id>
      <user-name>Jean-Hadrien Chabran</user-name>
      <creator-name>Jean-Hadrien Chabran</creator-name>
      <assigned-user-name>Ben Johnson</assigned-user-name>
      <url>http://binarylogic.lighthouseapp.com/projects/16601/tickets/112</url>
    </version>
    <version type="Ticket::Version">
      <assigned-user-id type="integer">22033</assigned-user-id>
      <attachments-count type="integer">0</attachments-count>
      <body>[state:&quot;moved_to_github&quot; bulk edit command]</body>
      <body-html>&lt;div&gt;&lt;p&gt;[state:&quot;moved_to_github&quot; bulk edit command]&lt;/p&gt;&lt;/div&gt;</body-html>
      <closed type="boolean">true</closed>
      <created-at type="datetime">2009-08-07T18:30:04-04:00</created-at>
      <creator-id type="integer">65234</creator-id>
      <diffable-attributes type="yaml">--- 
:state: new
</diffable-attributes>
      <milestone-id type="integer" nil="true"></milestone-id>
      <number type="integer">112</number>
      <permalink>attribute-with-multiple-parameters</permalink>
      <priority type="integer">0</priority>
      <project-id type="integer">16601</project-id>
      <state>moved_to_github</state>
      <tag nil="true"></tag>
      <title>Attribute with multiple parameters</title>
      <updated-at type="datetime">2009-08-07T18:30:04-04:00</updated-at>
      <user-id type="integer">22033</user-id>
      <user-name>Ben Johnson</user-name>
      <creator-name>Jean-Hadrien Chabran</creator-name>
      <assigned-user-name>Ben Johnson</assigned-user-name>
      <url>http://binarylogic.lighthouseapp.com/projects/16601/tickets/112</url>
    </version>
  </versions>
</ticket>
