Skip to content

Respect native QueryClient hashing for every query view #100

Closed

Description

@ueberBrot

Parent

Spec: Complete the review-driven Effect API Query 0.1.0 programme

What to build

Fetching, streamed publication, native reads, and native writes address one cache entry under client hashing defaults.

Acceptance criteria

  • Stop generated options from injecting a competing hash; QueryClient global/prefix defaults own hashing.
  • Preserve adapter-owned generated keys/functions and reject per-call explicit hashing that would split native key-only cache access.
  • Verify unary RPC/HTTP, infinite queries, and both streaming views with global and prefix custom hashes.
  • Assert one logical cache entry, working native reads/writes, and observed first-emission visibility.
  • Preserve frozen semantic keys and amend hash ownership, generated option types, and relevant ordinary runtime and public API compiler fixtures.

Metadata

Metadata

Assignees

Labels

ready-for-agentFully specified, ready for an AFK agent

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions