What's new in version 2 (part 1/4)
Loïc Poullain
Fullstack developper and creator of FoalTSThis article presents some improvements introduced in version 2 of FoalTS:
- the new CLI commands
- the service and application initialization
- the
AppController
interface - custom error-handling & hook post functions
- accessing file metadata during uploads
This article is the part 1 of the series of articles What's new in version 2.0. Part 2 can be found here.
#
New CLI commandsIn version 1, there were many commands to use, and this, in a specific order. Running and generating migrations from model changes required four commands and building the whole application needed three.
In version 2, the number of CLI commands has been reduced and they have been simplified so that one action matches one command.
#
Generating migrationsThis command generates migrations by comparing the current database schema and the latest changes in your models.
- Version 2
- Version 1
#
Running migrationsThis command builds and runs all migrations.
- Version 2
- Version 1
#
Build and run scripts in watch mode (development)If you want to re-build your scripts each time a file is change, you can execute npm run develop
in a separate terminal.
- Version 2
- Version 1
#
Revert one migrationThis command reverts the last executed migration.
- Version 2
- Version 1
#
Build migrations, scripts and the appThis command builds the application, the scripts and the migrations. Unit and e2e tests are not included.
- Version 2
- Version 1
#
Service and Application InitializationIn version 1, it was possible to add an init
method to the AppController
class and boot
methods in the services to initialize the application. These features needed special options in order to be activated.
Starting from version 2, they are enabled by default.
AppController
interface#
The This optional interface allows you to check that the subControllers
property has the correct type as well as the init
and handleError
methods.
#
Custom Error-Handling & Hook Post FunctionsIn version 1, when an error was thrown or rejected in a hook or a controller method, the remaining hook post functions were not executed.
Starting from version 2, the error is directly converted to an HttpResponseInternalServerError
and passed to the next post hook functions.
This can be useful in case we want to use exceptions as HTTP responses without breaking the hook post functions.
Example
#
Accessing File Metadata during UploadsWhen using the @ValidateMultipartFormDataBody
hook to handle file upload, it is now possible to access the file metadata.
Example
Property name | Type | Description |
---|---|---|
encoding | string | Encoding type of the file |
filename | string\|undefined | Name of the file on the user's computer |
mimeType | string | Mime type of the file |
path | string | Path where the file has been saved. If the saveTo option was not provided, the value is an empty string. |
buffer | Buffer | Buffer containing the entire file. If the saveTo option was provided, the value is an empty buffer. |
Stay up to date with the newsletter.