Configuration

Config file location

Schema Validator reads:

• plugins/Schema-Validator/config.yml

Current keys and behavior

[!NOTE] The strict-mode setting controls how the schema loader handles unsupported keywords:

• false (default): Logs a warning and continues loading the schema
• true: Throws an exception and aborts schema loading (fail-fast behavior)

[!NOTE] PluginConfig uses fallback defaults if a key is missing. For validation-on-load, bundled file is false, but code fallback is true if the key is removed.

Safe tuning strategy

1. Start with low-risk defaults

schema-directory: "schemas"
auto-load: true
cache-enabled: true
validation-on-load: false
strict-mode: false

2. Enable strict-mode in controlled environments first

Use strict-mode: true in CI/staging to catch unsupported keywords before production deploy.

3. Enable validation-on-load only after schema set stabilizes

validation-on-load validates each loaded schema using generated minimal test data. This can increase startup time and may flag complex schemas early.

4. Restart or reload and verify

After config changes:

1. restart server or run /sv reload --all
2. confirm config summary in logs
3. confirm schema load count
4. run one known validation command

Operational checklists

Production baseline

• auto-load: true
• cache-enabled: true
• strict-mode: true (recommended once schema set is stable)
• validation-on-load: false (unless startup checks are required)

Debug session baseline

• strict-mode: false
• validation-on-load: true

Continue

• Review administrative usage in Commands
• Compare keyword support details in Schema keywords
• Review runtime order in Validation behavior