Skip to content

Demonstrate shared native Query policy defaults #113

Closed

Description

@ueberBrot

Parent

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

What to build

Applications reuse QueryClient and generated-prefix defaults without breaking generated identity.

Acceptance criteria

  • Provide copied examples for common stale/retry policy, prefix defaults, and native call-site options.
  • Verify observable default merging and native reads/writes under the decided client hash contract.
  • Evaluate a narrow typed per-operation defaults map from actual repetition and adopt it only if it adds useful behavior.
  • Any helper retains generated key/function ownership and QueryClient hash ownership and has published type coverage.
  • Record a concrete native-only decision if a helper merely renames existing Query APIs.

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