> > I considered building a custom renderer, but I can’t figure how I’d pass > the schema into it.
I could also just use a vanilla decorator, but that covers up the view call > signature. I do similar stuff in a variety of ways. I almost-always augment the request object with an `add_request_method` that sets/stores/calculates the needed info for the active route. On some routes, that data is preloaded using a decorator, on others it is looked up as needed by calculating info from the request's matched_route. The second value to `render` methods of factory instances is `system` which should have the `request` object in it (reference the pyramid source or the cookbook for more info on that). So the request, and custom method, is easily available within the custom renderer. The big reason why I prefer using `add_request_method` to stash data like this is for ease in debugging. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/8e88d77f-1f80-41ff-847c-fdc1bd99ffec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
