#403 iterator overrules render in very flat app - merb-core

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
Combine keywords for powerful searching.
Use advanced searching »

#403 √ invalid

iterator overrules render in very flat app

Reported by schwabsauce | July 16th, 2008 @ 12:58 PM

In an action in the controller of my very flat app, if I call #each, the set I'm iterating over gets rendered. This happens whether or not a call to render exists anywhere in the action.

Comments and changes to this ticket

Michael Klishin (antares) July 16th, 2008 @ 02:49 PM
Could you post your code? It's probably how Merb handles action — anything returned from the action is sent to the client. In Ruby result of last statement in method body is returned, keep this in mind.
schwabsauce July 16th, 2008 @ 03:44 PM
With that in mind, it is likely that I just misunderstood how Merb handles rendering. I thought that you could effectively ignore the end of the action by conditionally rendering prematurely.
- flat_app_w_iterator.rb 533 Bytes
Michael Klishin (antares) July 16th, 2008 @ 03:59 PM
No, Merb has no auto rendering. Just returned string is used. That's the same reason why you have to make sure your action does not return nil which is not valid in rack.
Makes sense?
Yehuda Katz (wycats) July 19th, 2008 @ 10:37 PM
- → State changed from “new” to “invalid”