Stencil/Mustache parsing about vapor HOT 5 CLOSED

This seems like a great place to bring up middleware support for vapor.

Would we want support for adding middleware to:
- All requests
- A single route
- A group of routes

The Bootstrap class seems to be the place where middleware will hook into request and response to process what it needs to then pass it on. The problem I see is that in order to add support for multiple layers of middleware we would also need access to the next middleware in line inside both methods of Bootstrap. Also how middleware is ordered as it comes in from the request versus going out in the response should be decided.

Some links to where my thoughts/ideas are coming from:

SlimPHP's middleware docs
Lumen's middleware docs

from vapor.

I'm working on an update that replaces Bootstrap and adds a protocol called Middleware.

This will be in release 0.1.7.

The protocol looks like this

public protocol Middleware {
    func handle(handler: Request -> Response) -> (Request -> Response)   
}

And before the response is delivered in Server.swift

for middleware in self.middleware {
      handler = middleware.handle(handler)
}

from vapor.

Stencil parsing added in 0.1.8

from vapor.

@tannernelson vapor had stopped support for stencil template?

from vapor.

@yudun1989 the efforts required to run stencil on Linux were insurmountable for a long time w/o maintaining multiple forks in the dependency chain of Stencil. I'm not sure the current Linux status, but if it's improved, making a 3rd party stencil provider shouldn't be too difficult.

Unfortunately, these 3rd party renderers were requiring too much dev time internally, so it's very unlikely that we'll open up official support any time soon.

Hopefully this answers your question, and happy to open a discussion further if you'd like 👍

from vapor.