Skip to main content
mySpellChecker supports extension at multiple levels: configuration, custom providers, validators, segmenters, POS taggers, and algorithms.

Overview

mySpellChecker is designed for extensibility at multiple levels:

Configuration Extensions

Custom Configuration

Environment-Based Configuration

Custom Dictionary Providers

Built-in Providers

mySpellChecker includes four built-in providers:

Provider Interface

To create a custom provider, extend DictionaryProvider and implement all abstract methods:

Example: Redis Provider

Example: API Provider

Custom Validators

Validator Interface

Example: Domain-Specific Validator

Integrating Custom Validator

Custom Segmenters

Segmenter Interface

Example: ML-Based Segmenter

Custom POS Taggers

POS Tagger Interface

Example: Transformer-Based Tagger

Custom Grammar Rules

Grammar Rule Interface

Example: Custom Grammar Rule

Plugin Architecture

Note: The plugin system is a planned feature for future versions. The API shown below is subject to change.

Creating a Plugin

Registering a Plugin (Planned)

Best Practices

Extension Guidelines

  1. Follow interfaces: Implement all required methods
  2. Handle errors: Graceful degradation on failures
  3. Document behavior: Clear docstrings and examples
  4. Test thoroughly: Unit and integration tests
  5. Consider performance: Profile extensions

Performance Considerations

Error Handling

See Also