@/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.

3.11.0

Diff

rezonant

published 3.11.0 • 7 months ago

Changelog

Source

v3.11.0

@/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).

3.10.0

Diff

rezonant

published 3.10.0 • 7 months ago

Changelog

Source

v3.10.0

@/di
- You can now use Injector.run() to run a callback within an injection context for the given injector.

3.9.1

Diff

rezonant

published 3.9.1 • 7 months ago

Changelog

Source

v3.9.1

@/web-server
- The Session class is now exported properly.

3.8.0

Diff

rezonant

published 3.8.0 • 10 months ago

Changelog

Source

v3.8.0

@/web-server
- Route-specific middleware can now use WebEvent.current to acquire the web event being processed. While middleware has always had access to the request/response pair, the current WebEvent also provides access to the controller and method which is about to be executed, amongst other things. This enables middleware to introspect the method call that is about to occur, enabling a broad set of use cases that were previously impossible. NOTE: Global and controller-level middleware cannot access WebEvent.current as they occur before any Alterior-specific processing occurs.
- Alterior-style middleware classes are now resolved per request, allowing dependency injection providers to differ per call. This has been used to allow WebEvent to be dependency injected as an alternative way of acquiring it.
- The new preRouteMiddleware and postRouteMiddleware options allow you to specify route-specific middleware at the global and controller levels, enabling you to use the new introspection capabilities without specifying middleware on every route. The order of application is: (1) global pre-middleware, (2) controller pre-middleware, (3) route-specific middleware, (4) controller post-middleware, (5) global post-middleware.
- It is no longer necessary to mark middleware classes with @Middleware(). All classes are now treated as Alterior-style middleware (dependency injected, implements a handle() method). This is not a breaking change since passing a class not marked with @Middleware() would have caused a runtime error prior. As a result of this @Middleware() has been deprecated, and will be removed in 4.0.0.
- Correctness change: The type safety of the middleware-related properties of WebServerOptions, @Controller() and the @Route() family of decorators has been strengthened.
@/common: Adds leftPad(), rightPad(), zeroPad() and isConstructor()

3.7.5

Diff

rezonant

published 3.7.5 • 10 months ago

Changelog

Source

v3.7.5

@/web-server:
- Added the ability to override the default web server engine on specific @WebService classes
- Fixes an issue where installing Express' Typescript types alongside @/web-server may have been needed even though @/web-server does not have a direct dependency on Express
@/common: getParameterNames() will now look for a __parameterNames property and use that before trying to introspect the function, which allows code that transforms/replaces functions to carry parameter name metadata across more easily.
@/annotations:
- When running a mutator against a function, preserve parameter names by setting a __parameterNames property on the resulting function, containing the parameter names of the original function.
- Type safety has been improved around Mutator.create() and Mutator.define()