Releases: boostercloud/booster
v0.28.2
With this Booster version, by default, the full error stack trace is send to a local file, ./errors.log
. To see the full error stack trace directly from the console, use the --verbose
flag.
What's Changed
- Feature/94 remove stack trace from stdout by @davidverdu in #651
- fix: typecasted e from unknown to Error by @iyorozuya in #1011
- Documentation updates on latest changes by @tpellegrin in #1080
New Contributors
- @iyorozuya made their first contribution in #1011
- @tpellegrin made their first contribution in #1080
Full Changelog: v0.28.1...v0.28.2
v0.28.1
Fix regression issue that cause errors generating a new Booster project
What's Changed
- Update package.json template by @gonzalogarciajaubert in #1073
Full Changelog: v0.28.0...v0.28.1
v0.28.0
What's Changed
- A new GraphQL Generator is available thanks to @thomas-advantitge. You can check the original PR here #999.
- This new GraphQL Generator brings many improvements
- Supports required and optional ("?") fields
- Supports enums
- Supports union types
- Supports method return types (no need for @returns anymore)
- Supports Date type through a GraphQL Date scalar
Full Changelog: v0.27.1...v0.28.0
v0.27.1
The token verifier publicKey
is now a Promise<string>
instead of a string
to allow Booster to block the execution while verifying tokens. This is a small breaking change. You will need to upgrade your code to use a Promise or simple use Promise.resolve
. Example
publicKey: Promise.resolve(
fs.readFileSync(path.join(__dirname, '..', '..', 'assets', 'certs', 'public.key'), 'utf8')
),
What's Changed
- Promisified public key field in the token verifier config by @javiertoledo in #1067
Full Changelog: v0.27.0...v0.27.1
v0.27.0
Booster v0.27.0
New query filters
It is possible to filter read model queries using the isDefined
keyword. isDefined
will return a boolean indicating whether the property has a value assigned or not. Example:
query {
CartReadModels(filter: { price: { isDefined: true }) {
id
price
itemsIds
}
}
Migrations
A proof of concept has been enabled to migrate events and entities. This functionality may change in the future.
Global error handler
Booster includes a global error handler annotation @GlobalErrorHandler that will catch all errors that are thrown by:
- CommandHandlerErrors: Errors thrown by the handle method of the command. Program Handling Errors: Errors thrown by the handle method of the scheduled command. Event handling errors: Errors thrown by the handle method of the event.
- Reducer errors: Errors thrown by the @reduces method of the entity.
- Projection errors: Errors thrown by the ReadModel @Projects method.
- All errors: Errors thrown in any of the previous methods. This method will always be called, also when calling any of the above methods.
Scheduling commands
Scheduling commands are now available for the Local Provider. It is compatible with other scheduling commands supported by AWS and Azure providers.
What's Changed
- Add isDefined filter for Local, Azure and AWS Providers by @gonzalogarciajaubert in #1056
- Enable migration annotation for entities and events by @gonzalogarciajaubert in #1055
- Add GlobalErrorHandler by @gonzalogarciajaubert in #1049
- Add Scheduled Commands for Local Provider by @gonzalogarciajaubert in #1058
Full Changelog: v0.26.13...v0.27.0
0.26.13 - Array joinKey support in read model projections
v0.26.12
What's Changed
- Local Provider Search now uses AND as the default WHERE operator
Full Changelog: v0.26.11...v0.26.12
Add SortBy support for Azure and Local Providers
What's Changed
- Add SortBy support for Azure and Local Providers
See documentation
Full Changelog: v0.26.10...v0.26.11
Improve Local and Azure queries
What's Changed
- Add paginated queries to Local Provider
- Fix Local Provider queries with objects in the
includes
value - Fix Azure Provider nested queries
Full Changelog: v0.26.9...v0.26.10
Improved token verifications
What has changed
- If there is any expired token error while verifying the token then a
BoosterTokenExpiredError
error will be thrown. - If there is any NotBefore token error while verifying the token, a
BoosterTokenNotBeforeError
error will be thrown. - On any other token error, a NotAuthorizedError will be thrown.
Complete changelog: v0.26.8...v0.26.9