Modernize query filter syntax to object-based DSL

[Copilot]

ObjectQL's filter syntax required comprehensive modernization from array-based to object-based DSL per @objectstack/spec FilterCondition.

Changes

Type System (@objectql/types)

• Replace FilterExpression array type with FilterCondition object type from spec
• Update UnifiedQuery.filters signature and all dependent API types

Core Translation (@objectql/core)

• Implement translateFilters() converting FilterCondition → FilterNode arrays
• Add recursive convertFilterToNode() handling nested logical operators
• Map modern operators: $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, $contains, $startsWith, $endsWith, $null, $exist
• Support $and, $or logical composition
• Maintain backward compatibility for legacy array syntax

Testing

• 14 new tests covering operator combinations and edge cases
• All 290 core tests passing

Documentation

• Complete syntax reference with migration guide

Example

// Before
filters: [
  ['category', '=', 'Electronics'],
  'and',
  ['price', '>', 100]
]

// After
filters: {
  category: 'Electronics',
  price: { $gt: 100 }
}

// Complex queries
filters: {
  status: { $in: ['active', 'featured'] },
  price: { $gte: 100, $lte: 500 },
  $or: [
    { discount: { $gt: 0 } },
    { featured: true }
  ]
}

Architecture

Translation happens in core repository layer - drivers receive legacy FilterNode format unchanged. Zero driver modifications required.

Limitation: $not operator throws error (legacy format incompatible). Use $ne for field negation.

Security: CodeQL scan clean, type-safe implementation.

Original prompt

审视objectstack 最新的query filters语法规范，全面改造并不需要考虑向后兼容。

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
objectql-site	Ready	Preview, Comment	Jan 22, 2026 11:56am

[github-actions]

⚠️ No Changeset Found

This PR does not include a changeset file.
If this PR includes user-facing changes, please add a changeset by running:

pnpm changeset

[Copilot]

Pull request overview

This PR modernizes ObjectQL's query filter syntax from array-based to object-based DSL, following the @objectstack/spec FilterCondition specification while maintaining backward compatibility.

Changes:

• Type system updated to use FilterCondition from spec instead of array-based FilterExpression
• Core translation layer converts modern object syntax to legacy FilterNode format for drivers
• Comprehensive test suite added with 14 new tests covering operator combinations

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/foundation/types/src/query.ts	Replaces FilterExpression with Filter (FilterCondition) type and adds comprehensive documentation
packages/foundation/types/src/api.ts	Updates API interfaces to use new Filter type
packages/foundation/core/test/filter-syntax.test.ts	Adds test coverage for modern filter syntax translation
packages/foundation/core/src/repository.ts	Implements translateFilters() and convertFilterToNode() for syntax conversion
packages/drivers/sdk/src/index.ts	Updates SDK to use Filter type
docs/filter-syntax.md	Complete documentation of new syntax with migration guide

[Copilot]

The condition nodes.length > 0 || i > 0 could be simplified. Since we're adding 'and' before each operator except the very first node, consider restructuring to check if this is not the first overall node. The current logic may add an extra 'and' operator when processing the first field operator if nodes already contains logical operators.