feat: Better support for tools_strict=True when using the OpenAIChatGenerator

[sjrl]

Related Issues

• follow up to Fix component tool parameters #9342
• fixes feat: Better support for tools_strict=True when using the OpenAIChatGenerator #9411

Proposed Changes:

Added _strictify_function_schema function to enforce OpenAI's strict schema for tool specifications. This update affects the OpenAIChatGenerator component when tools_strict=True is enabled.

This function:

• recursively go through the parameters schema, find all type="object" schemas and add additionalProperties=False or remove it if it has no-required parameters
• recursively go through the parameter schema and remove any type: "object" parameters that don't have any required params --> this is not supported in strict mode

TODO:

• After removing all parameters have the schema {"type": "object", "additionalProperties": True} need to repair the remaining schema in case one of those removed parameters is a required parameter elsewhere. Look at test_strictify_function_schema_chat_message in test_openai.py to see a relevant example when ChatMessage is in the function schema.

How did you test it?

• Added new integration test

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I 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 documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 15132598341

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 15 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.03%) to 90.42%

---

Files with Coverage Reduction	New Missed Lines	%
core/pipeline/async_pipeline.py	3	67.32%
components/generators/chat/openai.py	12	94.26%

Totals
Change from base Build 15117961888:	-0.03%
Covered Lines:	10977
Relevant Lines:	12140

---

💛 - Coveralls