Michael Koziarski wrote: >> In my opinion that's enough evidence for use to seriously consider how we >> handle 303 in the framework. >> > > That's why I applied the patch for :status on redirect_to, I'm not > denying it deserves thought, just that it doesn't need a method ;) > > After all, it's just a one line method in application.rb if you want it for > now. > > def see_other(url) > redirect_to url, :status=>:see_other > end > First, thanks for the redirect_to patch. I started with that originally. Again because this is a common use case, I figured we need to address it in the framework, and it looked to me like the low hanging fruit is submitting a documentation patch. Documenting this means teaching people that for create actions they can't use simple redirect_to, but need to use redirect_to in a way that doesn't redirect the original request to the new resource, by following this pattern.
It took all of one read to realize this smells (I do consider documentation to be part of the code), and decide we better refactor it into a method. Actually it smelled like J2EE, you know that framework where instead of taking a stand and doing the right thing, it asks you to memorize a bunch of patterns and write boilerplate code all over the place? Assaf --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
