feat: expose deserialize_component_inplace

[davidsbatista]

Proposed Changes:

• deserialize_chatgenerator_inplace is a thin wrapper around deserialize_component_inplace (the actual logic), but only the wrapper is exported in haystack.utils

• 4 callers of deserialize_chatgenerator_inplace are deserializing something that isn't a chat generator:

  • opensearch/open_search_hybrid_retriever.py:344 (key="embedder")
  • elasticsearch/elasticsearch_hybrid_retriever.py:338 (key="embedder")
  • docling/converter.py:205 (key="meta_extractor")
  • langfuse/langfuse_connector.py:238 (key="span_handler")

How did you test it?

• No new tests needed — this is a pure export of an already implemented and tested private function

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ready	Preview, Comment	Jul 9, 2026 9:46am

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
haystack/utils
__init__.py
Project Total

This report was generated by python-coverage-comment-action