core-bundle
core-bundle copied to clipboard
add a twig function to get the rendered version of a route path
the idea is that this function would look at the configuration of the route to determine the controller/template etc
interesting idea. this could conflict a bit with the block concept - or we could wrap the thing into a block rather than a twig function? you would not want the exact same template to happen as with a full request, you need a clean html structure.
also is this not similar to a subrequest?
yes it would be a subrequest, but contrary to a normal render call, i would want to pass in a document path, rather than specifying a controller with specific parameters.
what about implementing this as a special type of block?
could work ..