Releases: raveljs/ravel
Release 1.0.0-rc.14
- Fix for #315
Release 1.0.0-rc.13
- Dependency update for core and dev dependencies, with a couple of exceptions due to stability issues
- Bugfix in logic for redis reconnection
Release 1.0.0-rc.12
- Fix for
SameSite
cookie issues, courtesy of #304 - Support for
PATCH
andHEAD
method types inRoutes
andResource
modules. See #306 for details. - Depedency update for all core and dev dependencies, with a couple of exceptions due to stability issues
- Defaulting to testing against Node 14, as it will be promoted to LTS this month
Release 1.0.0-rc.11
Adding error message indicating files which fail app.scan
.
Release 1.0.0-rc.10
-
Fix for wildcard-related routing issue (#292)
-
Deliberately supplying an undefined value as default for a registered parameter now causes an error to be thrown (#293):
const someVar = undefined;
app.registerParameter('my param', true, someVar); // this will now throw
This change is intended to catch cases where a default value is unintentionally undefined, but hard to spot as such because it is stored in a variable. A good example of this could be supplying an environment variable as the default value for a parameter (process.env.SOMETHING
), and then forgetting to supply the environment variable.
Release 1.0.0-rc.9
- Added ability to customize log format and colorization [#287]
Release 1.0.0-rc.7
This release contains a brand new, Ravel-specific router implementation to replace @koa/router
. This replacement addresses the inherent unpredictability of @koa/router
as applied in Ravel, where route declaration order is not clear to developers due to Ravel's dependency injection-focused approach. Routes are now ordered according to a more predictable system of priority.
This new router also addresses a serious, long-standing bug in @koa/router
. Now, only one route will be executed for a given request, chosen based on the above priority system.
A minor API-breaking change was required to support the new router:
// Previously, @mapping could be used to create a route that automatically responds with a status code
@mapping(Routes.GET, '/foo', 500)
// now, that is configured using a config object
@mapping(Routes.GET, '/foo', { status: 500 }) // necessary to support additional config parameters
Release 1.0.0-rc.6
Bugfix related to session storage. See #272 for details.
Release 1.0.0-rc.5
Additional configuration for session cookies, including:
app.set('session secure', true); // toggles Secure attribute for session cookies. true by default, and always true when app.get('https') is true.
app.set('session rolling', false); // force a session identifier cookie to be set on every response. The expiration is reset to the original maxAge, resetting the expiration countdown.
Release 1.0.0-rc.4
- Fix for #256