Why not either create a debug cookie or a some "debug" session data after the first instance, rather then take the brute force approach of rewriting every url... then just using ?debug=0 to later remove the debug cookie/debug session variable? I would think you could keep all the logic in a single filter then...
On Fri, Dec 5, 2008 at 9:36 PM, petemounce <[EMAIL PROTECTED]> wrote: > > So I'm writing a view-component that outputs some performance > information, and I'm also looking at the CombineJS component that > there's a patch for. I want to be able to launch an action in a > MonoRail site in debug mode - which would mean the performance view- > component would render as opposed to not, and the CombineJS component > would not minify JS or strip comments, so that it's possible to read > and step-through if necessary. > > So, I thought I'd add a debug=1 conditional. Fine, easy. > > Then I thought that, while I'm in debug mode, it would be nice if > everywhere I navigated to would also be in debug mode, so I don't have > to keep adding it to URLs and refreshing. What is my best bet for > doing that? I guess an AfterRendering filter that parses for hrefs > and so on, and then if it finds any, appends in my debug=1? I think > my other possibility is maybe subclassing the UrlHelper? What do you > think? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
