02:02 <FromGitter> <jwaldrip> Hey amber team. As im making improvements to Orion, I would hope that you could shed some light on something. I am debating between the trade off of variable isolation and just inlining the views. As of v3, the views are inlined. But with v4 I am change the interface to something like this: ⏎ ⏎ ```class MyController < Controller::Base``` [https://gitter.im/amberframework/amber?at=5f0d122e3c217837fd9998e4]

02:04 <FromGitter> <jwaldrip> locals assigns to a merged named tuple which keeps type and compile time safety

02:05 <FromGitter> <jwaldrip> and also still maintains a security layer between the view and controller

02:06 <FromGitter> <jwaldrip> thoughts?

04:07 <FromGitter> <eliasjpr> I like the approach a lot @jwaldrip now I do think it would be overkill to always specify the vars can you simply make it a **args parameter? This way simply have to pass a namedtuple

04:29 <FromGitter> <mixflame> hey Amber friends

04:29 <FromGitter> <mixflame> I'm glad this is still going

14:00 <FromGitter> <andrewc910> @jwaldrip how are you actually rendering the view? I took a look rendering in amber and couldn't find a suitable way to change the render macro.

14:20 <FromGitter> <jwaldrip> come magic with the run macro ;-)

14:21 <FromGitter> <jwaldrip> ```code paste, see link``` [https://gitter.im/amberframework/amber?at=5f0dbf78343f5d69494c9056]

14:22 <FromGitter> <jwaldrip> ```code paste, see link``` [https://gitter.im/amberframework/amber?at=5f0dbfb90d37916fda748a23]

14:24 <FromGitter> <jwaldrip> @eliasjpr its a macro that relies on named args already, without restricting certain keys I couldnt do a doublesplat