Getting started: Create new component
DetectMateLibrary includes a small CLI helper to bootstrap standalone workspaces for custom parsers and detectors. This is useful if you want to develop and test components in isolation while still using the same library and schemas.
Usage
The CLI entry point is mate with a create command:
mate create --type <parser|detector> --name <workspace_name> --dir <target_dir>
| Option | Description |
|---|---|
--type |
Component type to generate: - parser: CoreParser-based template- detector: CoreDetector-based template |
--name |
Name of the component and package: - Creates package dir: <target_dir>/<name>/- Creates main file: <name>.py- Derives class names: <Name> and <Name>Config |
--dir |
Directory where the workspace will be created |
What gets generated
For example:
mate create --type parser --name custom_parser --dir ./workspaces/custom_parser
will create:
workspaces/custom_parser/ # workspace root
├── custom_parser/ # Python package
│ ├── __init__.py
│ └── custom_parser.py # CoreParser-based template
├── tests/
│ └── test_custom_parser.py # generated from template to test custom_parser
├── data.json # example data to run the code
├── LICENSE.md # copied from main project
├── .gitignore # copied from main project
├── .pre-commit-config.yaml # copied from main project
├── pyproject.toml # minimal project + dev extras
└── README.md # setup instructions
Add component to DetectMateLibrary
To add the new component to the DetectMateLibrary, you need to add the component file to the specific folder and update the import paths.
- Detector: Add the detector file component in
src/detectmatelibrary/detectorsand the unit tests intests/test_detectors. - Parsers: Add the parser file component in
src/detectmatelibrary/parsersand the unit tests intests/test_parsers.
Once that is complete, ensure that all unit tests and the pre-commit process are successful.
Go back to Index, to previous step: Basic usage.