Skip to content

fix: restrict addable scalar field types - #11

Merged
egolearner merged 1 commit into
zvec-ai:mainfrom
copacabanaservice01:fix/numeric-scalar-field-types
Sep 3, 2026
Merged

egolearner merged 1 commit into
zvec-ai:mainfrom
copacabanaservice01:fix/numeric-scalar-field-types

Conversation

@copacabanaservice01

@copacabanaservice01 copacabanaservice01 commented Sep 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • limit the Add Scalar Field selector to the numeric types supported by Zvec add_column
  • default new scalar fields to INT32
  • reject unsupported post-creation field types at the API validation boundary
  • preserve duplicate-field coverage with a supported numeric field

Testing

  • pnpm --filter frontend lint
  • pnpm --filter frontend typecheck
  • pnpm --filter frontend test (329 passed)
  • pnpm --filter frontend build
  • uv run ruff check zvec_studio/schemas/collection.py tests/unit/test_collections_schemas.py tests/integration/test_collections_router.py
  • uv run mypy zvec_studio
  • uv run pytest -q (575 passed, 4 skipped on Windows)

Closes #10

Signed-off-by: copacabanaservice01 <copacabanaservice01@gmail.com>
@egolearner
egolearner merged commit 3469990 into zvec-ai:main Sep 3, 2026
15 checks passed
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.

Add Scalar Field defaults to unsupported STRING type

2 participants