Skip to content

Resolve typed partial-invalidation ergonomics #114

Closed

Description

@ueberBrot

Parent

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

What to build

Consumers have a precise supported approach to operation and partial-input filtering while exact keys remain canonical.

Acceptance criteria

  • Prototype focused filters against generated root/branch/leaf/operation identities and concrete data-tagged keys.
  • Define meaningful partial matching for constructor defaults, custom encoders, and supported request/payload shapes; expressly limit ambiguous cases.
  • Verify exact/prefix behavior and stable broad invalidation for retained stream policies.
  • Adopt a narrow public helper only for demonstrated type-safe value; otherwise publish the tested native-filter recipe and bounded limitation decision.
  • Amend the filter-composition decision if the public contract changes and prove any export through ordinary factory runtime tests 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