Skip to content

refactor(query): use string filter operands - #40

Merged
meaningforger merged 1 commit into
mainfrom
codex/string-filter-operands
Oct 10, 2026
Merged

meaningforger merged 1 commit into
mainfrom
codex/string-filter-operands

Conversation

@meaningforger

Copy link
Copy Markdown
Contributor

Summary

  • accept only string or string-array values at REST, MCP, CLI, validation, and regression query boundaries
  • resolve literals from semantic datatypes into typed Integer, Decimal, Float, Boolean, and temporal database parameters
  • keep structured AND/OR/NOT/EXISTS predicates without adding raw SQL or expression parsing
  • align MCP schemas, definition filters, examples, conformance fixtures, and documentation
  • remove YAML numeric-token restoration that is no longer needed

Validation

  • go test ./...
  • make docs-check vet
  • make test-samples
  • make ci-contract-check

@meaningforger
meaningforger merged commit e6a122e into main Oct 10, 2026
3 of 4 checks passed
@meaningforger
meaningforger deleted the codex/string-filter-operands branch October 10, 2026 01:13
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