cocosearch-add-extractor

To add a language dependency extractor to CocoSearch, follow the workflow covering pre-checks, extractor implementation, optional module resolver, tests, and registry registration. This enables forward edges in the dependencies graph for the new language.

A dependency extractor workflow involves pre-checks to validate viability, implementing the extractor, adding an optional module resolver, writing tests, and updating the registry. This process enables dependency graph forward edges and related code-analysis tooling.

You need a dependency extractor when adding support for a new language or grammar to CocoSearch, enabling forward edges in the dependencies graph and related tooling. Pre-checks validate the extractor viability before implementation.

A module resolver is optional when adding a language dependency extractor. The core workflow requires pre-checks, extractor implementation, tests, and registration, but the module resolver can be integrated if needed for the specific language.

New dependency extractors are registered and tested using existing extractor patterns and autodiscovery. The workflow guides you through writing tests and updating the registry to ensure the new language extractor is validated and properly integrated.