Ban constraint fields IChatGptSchema
.
#86
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to input JSON files, schema JSON files, and TypeScript files. The main focus is on updating input data formats, refining schema definitions, and adjusting TypeScript configurations.
Input JSON files updates:
chatgpt
,claude
, andgemini
inexamples/function-calling/arguments
directory. [1] [2] [3] [4]Schema JSON files updates:
chatgpt
,claude
, andgemini
inexamples/function-calling/schemas
directory. [1] [2] [3]claude.sale.schema.json
.TypeScript files updates:
ChatGptConverter
to use a new configuration format that includesreference
andconstraint
properties. [1] [2]GeminiConverter.ts
and adjusted logic to handle object properties more efficiently. [1] [2]OpenApiContraintShifter
import and updatedLlmConverterV3
to handle numeric and string constraints based on the new configuration. [1] [2]LlmSchemaConverter.ts
to remove theconstraint
property.IChatGptSchema
inIChatGptSchema.ts
. [1] [2] [3] [4] [5] [6] [7]Package update:
package.json
to2.0.0-dev.20241125-2
.