fix: return full pagination object in execute_query responses

[fuleinist]

Stacked on #57 — this branch is based on fix/get-tables-parallel-describe. Only the top commit (fix: return full pagination object) is new; the diff shrinks to a single commit once #57 merges.

Summary

The Tabularis app (0.17+) deserializes execute_query results into a QueryResult whose Pagination struct requires page, page_size, total_rows (optional) and has_more (src-tauri/src/models.rs). The plugin only sent:

"pagination": {"next_token": "..."}

so the app rejected every query response with missing field \page`— and after patching that,missing field `page_size`, then missing field `has_more``. Query results never rendered in the UI.

Changes

• items_to_response now always emits a complete pagination object:
  • page — request's page param (default 1, new extract_page helper)
  • page_size — request's limit, falling back to the returned row count
  • total_rows — null (DynamoDB cannot cheaply count a filtered result)
  • has_more — existing next_token/truncation logic, unchanged
  • next_token — preserved alongside for resume
• Aggregate responses (COUNT/SUM/...) keep pagination: null, which the app's Option<Pagination> accepts.
• Regression tests: pagination shape, app-contract fields, extract_page defaults.

Test plan

• cargo test — 178 passed (3 new)
• cargo clippy — clean
• End-to-end against the real app + a live AWS account: query results render, paging works

No credentials, endpoints, or account-specific data included in this change.

Made with Cursor

Made with Cursor