History edits for 0.5.7
fix functional tests after refactor on tunnel
upgrading to 3.9.1 to solve the issue with handlebars
enable per-request tunnel url configuration
The configurable `tunnelUrl` value will still be validated against `tunnelPrefix`, which can be configured in application.json and defaults to `/tunnel`.
refactor tunnel middleware into two phases
With unit tests!
Uses the convention where a middleware with an arity of 4 is assumed to be the error handler.
- Remove trailing slashes from tunnel/static prefixes. - Add flag and flag check to determine when to stop processing the request.
- Replaced the brittle `trimSlash` stuff with `require('path').normalize`.
- delay object creation for performance reasons - use core library methods for parsing url/path - fix http response code (500 => 404) - eliminate `that = this` usage by closing over prefix variables directly
By splitting the tunnel logic into a detection phase and a handling phase, applications are free to override the handling logic. In order to maintain backwards-compatibility, instead of refactoring the existing tunnel middleware, a tunnel-demux middleware to detect the type of tunnel request, and tunnel-(rpc|specs|type) middleware to handle each type of request have been added. Mojito itself will now use these new middleware in place of the single tunnel middleware, which will remain for those applications that are specifying it in their configuration.
fix bz6160815: port argument must be an integer
restoring custom arrow config, this should fix jenkins, hopefully!
upgrading to yui 3.9.0
… default one shipped with arrow which is 3.6.0 at the moment.
[doc] Fixed screenshot for an example and modified documentation explaining the screenshot.