Repository navigation
Fixes non-secured default routes and fixes inline template renders
If for some reason the default route was unsecured, it would not work as expected. So now you can specify the default_route to be unsecured and behave as expected.
Also inline template renders I don't think worked as expected. Right now inline templates won't be rendering through the EPL engine but you can still render a block of raw text/html -- or you can use EPL syntax but it'll get resolved at app bootstrap via the JSONConfig plugin... not per request. The change here is to the routing syntax, e.g. template_name => "inline: <b>Text Here</>" whereas omitting the inline: prefix will make the app look for an actual template file of that name.