Publish 2.0.0

[greguintow]

What does this PR do?

• Publish 2.0.0 with support to infer class-validator decorators

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• ^(?!main$|master$).*$

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fireflies-bot]

🔍 PR Complexity Assessment

🟡 Risk Score: 4/10

[████░░░░░░]

📝 Summary

This PR publishes version 2.0.0 of the @firefliesai/schema-forge library, adding Date type support with date-time format, class-validator decorator integration for automatic JSON Schema constraint inference, and new validation constraint options in the ToolProp decorator.

📊 Lines Analysis

Metric	Count
Total Changes	1028
Production Code	838
Test Code	190

💡 Recommendation

Review the class-validator integration logic in class-validator-integration.ts and ensure the decorator property inference precedence (explicit ToolProp options over class-validator inferred values) works correctly. Verify the Date type handling doesn't break existing consumers. The changes are well-tested but given the major version bump, consider impact on downstream services.

---

_{This assessment is automated and should be used as a guide. Please use your judgment when reviewing.}

[devin-ai-integration]

Devin Review found 1 potential issue.

View issue and 5 additional flags in Devin Review.

[devin-ai-integration]

🟡 prepareForOpenAIStructuredOutput doesn't strip constraints for 'integer' type

When a property has type: 'integer' (set via @IsInt() class-validator decorator or explicit type: 'integer' in @ToolProp), the minimum, maximum, and multipleOf properties won't be stripped when converting to OpenAI structured output format.

Click to expand

Issue Details

The prepareForOpenAIStructuredOutput function in utils.ts only checks for type === 'number' when deciding whether to strip unsupported numeric constraints:

} else if (
  newObj.type === 'number' ||
  (Array.isArray(newObj.type) && newObj.type.includes('number'))
) {
  // Remove unsupported number properties
  ['minimum', 'maximum', 'multipleOf'].forEach((prop) => {
    if (prop in newObj) delete newObj[prop];
  });
}

However, the PR introduces support for type: 'integer' via:

1. @IsInt() class-validator decorator (class-validator-integration.ts:152)
2. Explicit type: 'integer' in @ToolProp options (types.ts:40)

Impact

When using OpenAI structured output with integer types that have constraints, the schema will contain minimum/maximum properties that OpenAI's structured output mode doesn't support, potentially causing API errors or unexpected behavior.

Expected vs Actual

• Expected: minimum, maximum, multipleOf should be stripped for both number and integer types when forStructuredOutput: true
• Actual: These constraints are only stripped for number type, not integer

(Refers to lines 93-100)

Recommendation: Add a check for 'integer' type alongside 'number':

} else if (
  newObj.type === 'number' ||
  newObj.type === 'integer' ||
  (Array.isArray(newObj.type) && (newObj.type.includes('number') || newObj.type.includes('integer')))
) {

---

Was this helpful? React with 👍 or 👎 to provide feedback.