Skip to content

fix(schema): infer integer type for Nimble enum choices#611

Closed
mhsdef wants to merge 1 commit intoagentjido:mainfrom
mhsdef:fix/nimble-integer-enum-type
Closed

fix(schema): infer integer type for Nimble enum choices#611
mhsdef wants to merge 1 commit intoagentjido:mainfrom
mhsdef:fix/nimble-integer-enum-type

Conversation

@mhsdef
Copy link
Copy Markdown
Contributor

@mhsdef mhsdef commented Apr 14, 2026

Description

When a Nimble :in type contains all integer choices (e.g. {:in, [1, 2, 3]}), the generated JSON schema now correctly emits "type": "integer" instead of always defaulting to "type": "string".

Type of Change

  • Bug fix (non-breaking change fixing an issue)
  • New feature (non-breaking change adding functionality)
  • Breaking change (fix or feature causing existing functionality to change)
  • Documentation update

Breaking Changes

N/A

Testing

  • Tests pass (mix test)
  • Quality checks pass (mix quality)

Checklist

  • My code follows the project's style guidelines
  • I have updated the documentation accordingly
  • I have added tests that prove my fix/feature works
  • All new and existing tests pass
  • My commits follow conventional commit format
  • I have NOT edited CHANGELOG.md (it is auto-generated by git_ops)

Related Issues

N/A

When a Nimble `:in` type contains all integer choices, the generated
JSON schema now correctly uses `"type": "integer"` instead of always
defaulting to `"type": "string"`.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@mhsdef
Copy link
Copy Markdown
Contributor Author

mhsdef commented Apr 14, 2026

Omg. Need to run these more locally first. Maybe we need both?

@mhsdef mhsdef closed this Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant