@/web-server
- It is now possible to access WebEvent.current within custom log formatters and request reporters.
- It is now possible to subclass HttpError and have Alterior handle it as expected. This was not possible prior due to issues long since solved with how extended Error works (when Alterior targeted ES5, this was not possible in Typescript 2.1 or later). Since this is no longer an issue, this restriction has been lifted.

3.8.1

published 3.8.1 • 7 months ago

3.9.5

published 3.9.5 • 7 months ago

published 3.10.3 • 7 months ago

published 3.11.2 • 7 months ago

Changelog

published 3.11.1 • 7 months ago

Changelog

@/web-server
- Adds globalMiddleware option to @Controller(). This has the same semantics as middleware in previous releases, but with clarified naming.
- The middleware option of @Controller() is now deprecated in favor of globalMiddleware.
- Fixes a problem where JSON strings cannot be used with the new @Body({ type: 'json' }) feature because of body-parser's "strict mode". Disabled "strict mode" when using the JSON mode of the body-parser middleware internally.

published 3.11.0 • 7 months ago

Changelog

@/annotations
- Improves the return type of Annotation.decorator() so that it is dependent on the provided valueTargets (when possible). Issue
@/web-server
- Adds ability to override the body parser in use via the @Body() decorator. This is useful for cases like trying to accept JSON strings (since string normally causes a text body parser to be used).

published 3.10.2 • 7 months ago

Changelog

@/web-server
- Fixes an issue where a request's body will be unparsed if the Content-Type passed does not match the typical content type associated with the expected body format. For instance, when expecting JSON (the default), the body would only be parsed when the Content-Type header was application/json. When expecting text (ie when @Body() has type string), the body would only be parsed when the Content-Type header was text/plain. This is unexpected, since Alterior provides no manner to validate the Content-Type field without using custom middleware. Now the body is parsed as the expected type regardless of Content-Type.