title: future proofing rails partials calling scheme
body: <p>I'm porting a php app to rails and am wondering what the best practice for having the most flexibility in a rails partial is. I saw a lot of "you could do it like this"</p>
  
  <p>I'm thinking like this:  </p>
  
  <pre><code>&lt;%=render :partial =&gt; 'shared/show_info', 
      :locals =&gt; { 
          :info =&gt; x , 
          :hide_location =&gt; true} %&gt;
  </code></pre>
  
  <p>where use a :locals even if only one argument. </p>
  
  <p>Any ideas on whether this would be the best way for maximum scalability in the future or why this would not be a good idea?</p>
  
  <p>thx</p>
  
  <p>edit #1
  added the shared/_show_info.html.erb  - this would be the type of thing I'd be doing :hide_location which takes out the location </p>
  
  <pre><code>&lt;% if !local_assigns.has_key? :hide_location %&gt;
    &lt;%=info[:location] %&gt;
  &lt;% end %&gt;
  </code></pre>