Databases
StackOverflow2013
Postsdbo
PORails: Refactoring, views, helpers: how does it all go together?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails: Refactoring, views, helpers: how does it all go together?
    primarykey
    data
    text
    <p>Warning: Noob here.</p> <p>I know this is a trivial subject but I'm having a lot of difficulty in figuring out how exactly I can simplify my views by moving parts of them into helpers. For example, I've always read that conditionals in your views are prime candidates for extraction into helpers, but I couldn't really find examples of this, and my attempts to achieve this failed.</p> <p>For example, suppose I have:</p> <pre><code>#index.html.erb &lt;% for beast in @beasts do -%&gt; &lt;% if beast.dead? -%&gt; &lt;%= beast.body %&gt; &lt;%= link_to "bury", bury_beast_path( :id =&gt; beast.id ) %&gt; &lt;% else -%&gt; &lt;%= beast.body %&gt; &lt;%= link_to "kill!", kill_beast_path( :id =&gt; beast.id ) %&gt; &lt;% end -%&gt; &lt;% end -%&gt; </code></pre> <p>It annoys me a little to have this in my view, but how exactly could I move this to a helper instead? And further simplify it, if possible. (I've read somewhere that conditionals are bad but it's just beyond me how you could program anything without them.)</p> <p>Another example: I need to <code>id</code> my <code>body</code> tags with the format <code>controller_action</code>. The best I've got so far is this:</p> <pre><code>#index.html.erb &lt;body id="&lt;%= controller_action %&gt;"&gt; </code></pre> <p>…and…</p> <pre><code>#application_helper.rb def controller_action @id = @controller.controller_name + "_" + @controller.action_name end </code></pre> <p>I'm no expert, but that's still ugly even to me. </p> <p>To make things more complicated, <a href="http://37signals.com/svn/posts/1952-i-gave-a-talk-on-ui-fundamentals-for-programmers" rel="noreferrer">Ryan Singer said something I liked</a>: to treat ERB like an image tag, using helpers to "reveal intention". Then in the next breath saying that you should have no HTML in helpers for that is the way to hell. WTF? How are both things compatible? If it's come to the point where you can just declare behaviors in the view, surely there should be a lot of HTML to be rendered behind the scenes? I can't grasp it.</p> <p>So, that's basically it. I'd appreciate if anyone could share some thoughts on this, or point me to some good in depth reading on the subject – which I've found to have a really weak coverage on the web. I've already googled it to exhaustion but who knows.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USSan Diago
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails: Refactoring, views, helpers: how does it all go together?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails: Refactoring, views, helpers: how does it all go together?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails: Refactoring, views, helpers: how does it all go together?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMinor note. Using `for` is fine, but using an iterator is more Ruby convention, e.g., `<% @beasts.each do |beast| %>`.
      singulars
      1. PORails: Refactoring, views, helpers: how does it all go together?
      1. USSarah Vessels
    2. CO@Sarah: Thanks. It's that I just really like the natural language aspect of using `for`.
      singulars
      1. PORails: Refactoring, views, helpers: how does it all go together?
      1. USSan Diago
 

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