Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix ChatGptSchemaComposer's strict mode #145

Merged
merged 1 commit into from
Feb 24, 2025
Merged

Fix ChatGptSchemaComposer's strict mode #145

merged 1 commit into from
Feb 24, 2025

Conversation

samchon
Copy link
Owner

@samchon samchon commented Feb 24, 2025

This pull request includes several changes to the ChatGptSchemaComposer and introduces a new test for the strict schema validation. The most important changes are the refactoring of the transform function to take a configuration object and the addition of a new test file.

Refactoring and improvements to ChatGptSchemaComposer:

  • src/composers/llm/ChatGptSchemaComposer.ts: Refactored the transform function to accept a configuration object, allowing for more flexible schema transformations. This change affects multiple parts of the file, including how $defs and other schema properties are processed. [1] [2] [3] [4] [5]

Version update:

  • package.json: Updated the package version from 2.5.1 to 2.5.2.

New test for strict schema validation:

@samchon samchon added bug Something isn't working enhancement New feature or request labels Feb 24, 2025
@samchon samchon self-assigned this Feb 24, 2025
Copy link
Owner Author

@samchon samchon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test OK

@samchon samchon merged commit 2930f4d into master Feb 24, 2025
4 checks passed
@samchon samchon deleted the feat/strict branch February 24, 2025 12:24
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant