Skip to content

fix(analyzer): preserve LangExtract YAML options#2162

Closed
hexsm wants to merge 2 commits into
data-privacy-stack:mainfrom
hexsm:fix/langextract-yaml-config-path
Closed

fix(analyzer): preserve LangExtract YAML options#2162
hexsm wants to merge 2 commits into
data-privacy-stack:mainfrom
hexsm:fix/langextract-yaml-config-path

Conversation

@hexsm

@hexsm hexsm commented Jul 13, 2026

Copy link
Copy Markdown

Change Description

Preserve LangExtract recognizer constructor options when loading recognizers from YAML registry configuration.

This adds dedicated YAML validation models for:

  • BasicLangExtractRecognizer, preserving config_path
  • AzureOpenAILangExtractRecognizer, preserving config_path, model_id, azure_endpoint, api_key, and api_version

Previously these fields were dropped during Pydantic validation / serialization, so the registry loader could not pass them to the recognizer constructors.

A changelog entry and regression tests were added.

Issue reference

N/A

Checklist

  • I have reviewed the contribution guidelines
  • I agree to follow this project's Code of Conduct
  • I confirm that I have the right to submit this contribution and that it does not knowingly contain proprietary or confidential code.
  • My code includes unit tests
  • All unit tests and lint checks pass locally
  • My PR contains documentation updates / additions if required

@hexsm

hexsm commented Jul 13, 2026

Copy link
Copy Markdown
Author

I noticed that this PR duplicates the changes already covered by #2157, which preserves LangExtract recognizer YAML options during recognizer registry validation.

To avoid splitting review effort, I’m closing this PR in favor of #2157.

@hexsm hexsm closed this Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant