Thanks, but it doesn't really solve the problem with having to repeat constraints from the outer scope. Additionally, in my case the "Authenticated" constraint is used in few other places as well, so I'd have to name this particular one e.g. AuthenticatedSubdomain and that will pretty soon became really awkward with deeper nesting. The wrapper class solves the problem with naming and reusing the same constraint classes, but doesn't solve the problem of repeating constraints.
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/3vVRucPp6gAJ. 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-talk?hl=en.
