✨Style and structure guide
This page describe the preferred code style and folder structures of a module
Code formatting
By default a Multijet project uses Prettier as a code formatter, customizable with the root configuration file:
Editor configuration
If you are using VSCode, multijet includes a default configuration (located in the .vscode
folder) that includes recommended extensions, debug configurations and formatting settings.
It is highly recommended to use Conventional Commits as a standard for all Git commits.
Modules file structure
It is suggested to follow a standard file structure when developing shared libs.
The followings are examples of how you can structure your libraries in order to make them more consistent and readable.
It's important to write interfaces so you can decouple the implementation of your library or module. All shared libs or modules, if possibile, should export at least one interface and one implementation for that same interface.
If your library needs to be divided in submodules you can follow the same structure as follows:
The library index.ts
should only contain exports for the modules and interfaces you want to export, nothing more.
The following is a real example of a small lib:
Last updated