Fix TypeScript error in useQueryBuilder test

[Copilot]

CI failing on tsc --noEmit due to accessing property on unknown type.

serializeFilterTree() returns unknown | null per ObjectQL spec (supports multiple array shapes). Test mock returns structured object but TypeScript doesn't know this.

Changes

• Add SerializedFilter interface matching mock return type
• Use typed assertion: (serialized as SerializedFilter).logic

interface SerializedFilter {
  logic: string;
  filters: Array<{
    field: string;
    operator: string;
    value: string;
  }>;
}

// In test:
expect((serialized as SerializedFilter).logic).toBe("AND");

Original prompt

引用: https://github.com/objectstack-ai/mobile/actions/runs/21832572220/job/62994778979#step:6:1

fix all ci build and test

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This PR addresses a TypeScript compile error in the useQueryBuilder hook test by introducing a local type for the mocked serialize() output and casting the unknown return value to access logic.

Changes:

• Add a SerializedFilter interface in the test file to describe the mocked serialized shape.
• Update the serialization assertion to use a type assertion when accessing logic.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

expect(serialized).toBeDefined() doesn’t exclude null (null is “defined”), so if serialize() ever returns null this test will throw when accessing .logic rather than failing with a clear assertion. Prefer asserting non-null (e.g., not.toBeNull() / not.toBeNull() + type guard) or use an objectContaining({ logic: "AND" }) matcher to avoid unsafe property access on unknown.

[Copilot]

The new SerializedFilter interface suggests the real ObjectQL serialization format is an object with logic/filters, but the production serializeFilterTree() returns an array-based AST (unknown | null). To avoid confusion, consider renaming this to something test/mock-specific (e.g., MockSerializedFilter) or switching the expectation to structural matching without introducing a misleading type name.