File¶
As ddb work on files, there is a dedicated feature which soul purpose is to walk through files from the project directory and trigger events when files are found or removed.
Feature configuration (prefixed with jinja.)
| Property | Type | Description |
|---|---|---|
disabled |
booleanfalse |
Should this feature be disabled ? |
extensions |
string[] | A list of glob of supported extension. |
includes |
string[] | A list of glob of directories to include. |
excludes |
string[]['**/_*', '**/.git', '**/.idea', '**/node_modules', '**/vendor', '**/target', '**/dist'] |
A list of glob of directories to exclude. |
include_files |
string[] | A list of glob of files to include. |
exclude_files |
string[] | A list of glob of files to exclude. |
File walk and event triggering¶
As previously said, the soul purpose of the feature is to walk through files from the project directory, recursively.
It does not dive into folders set in file.excludes configuration.
For instance, the directory node_modules which contains npm installed modules on the project is not process.
By doing so, the feature is faster.
When it checks for a folder, each file not excluded is put into a file:found event which will be caught by other
features such as jsonnet or docker feature, and store those file in ddb cache.
For next executions, using this cache, the feature will detect if a file have been deleted and raise a file.deleted.
This event is used by the gitignore feature to remove the file from the gitignore if needed.
The watch mode
This feature is the one that will benefit the most from the watch mode described in the command section.
It will then be kept active and check if a file is created, modified, moved or even deleted.