On Fri, Sep 7, 2012 at 2:32 PM, George Ogata <george.og...@gmail.com> wrote:
> On Fri, Sep 7, 2012 at 5:15 PM, Robert Pankowecki < > robert.pankowe...@gmail.com> wrote: > >> > Can you provide more info on what you're doing with this searched word? >> > Highlighting? >> >> I was just using it for coherent navigation. You could go like search >> => show => edit => update => index and see the list filtered with the >> searched keyword. >> > > Understood. I wonder if a cookie scoped to that path would be another > alternative - shouldn't be affected by other tabs, at least. > > > i.e., keep the common case clean, at the expense of making the unusual >> case >> > a bit more work. >> >> I agree. Just didn't want the unusual case to be impossible after some >> refactoring. > > > Cool - totally valid point. > If someone is considering re-working flash message behavior, I'd like to throw in my +1. I previously encountered issues with them (Some examples of bugs: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4082-flash-loses-messages-on-redirect) and landed on a solution much like George Ogata describes, which is simple to implement and much less error-prone. flash[:foo] is saved only for the duration of a request if rendering occurs, but contents are stored if a redirect occurs. -Greg -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
