Disclose an unsettled post-gesture surface on selector-targeted interactions
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- mobile-dev, testing
Línea de trabajo
Start by reading src/commands/interaction/runtime/resolution.ts around lines 733-752 where captureSnapshot is called. Understand how selector-targeted interactions like click and press resolve. Then examine src/daemon/deferred-interaction-outcome.ts to see how SnapshotState.unsettledGesture is set, and src/daemon/capture-disclosure.ts to see how selector reads disclose this fact. The goal is to modify the resolution logic to also disclose unsettledGesture when a target is missing from a tree with that fact, matching the behavior of selector reads.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
#2839 makes a post-gesture capture that never settled carry unsettledGesture, and discloses it on selector reads (is, get, find, wait) and snapshot. Selector-targeted interactions do not disclose it yet. click, press, fill, and similar commands resolve their target through src/commands/interaction/runtime/resolution.ts (the captureSnapshot call near lines 733-752). After a scroll whose surface is still moving, a target missing from that tree fails as a plain not-found. The agent cannot tell this apart from a real absence.
Expected
An interaction whose selector resolution misses on a tree with unsettledGesture carries the same typed unsettledGesture fact and warning as the selector reads. It must be keyed on the tree fact and must not match on message text.
Notes
- The fact is stamped on
SnapshotState.unsettledGesturebycapturePostGestureStabilizedResult(src/daemon/deferred-interaction-outcome.ts). - The selector reads disclose it through
withCaptureDisclosures(src/daemon/capture-disclosure.ts). - Follow-up to #2839.
- Lenguaje dominante
- TypeScript
- Estrellas
- 4.7k
- Forks
- 304
- Merge medio
- 11 h 46 min
- PR fusionados (30 d)
- 496
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstack/agent-device
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
callstack/agent-device#2842 ·
-
docs(ios-runner): RUNNER_PROTOCOL.md points at the wrong file and omits recovery and busy codes Abiertodocumentation good first issue ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
callstack/agent-device#2797 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
callstack/agent-device#1869 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
callstack/agent-device#2856 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
callstack/agent-device#2833 ·
Todos los issues de callstack/agent-device
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
TanStack/tanstack.com#1293 ·