Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Link state errors to the operation that established the relevant state

Abierto
  • ¿Algo no está bien?
#298 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
compilers, devtools

Línea de trabajo

Start with the E_A3_07_ScannerOutputStage example and trace how verifier provenance metadata reaches the error DTO and extension link. Check how state transitions and @StateSet/@StateRefinement information are currently represented, then verify the acceptance cases: preserved origins, separate receiver origins, constructor origins, and no link for ambiguous branches. Confirm that existing verification results remain unchanged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement error messages future ide

Problem

A state error points to the rejected call, but often leaves the developer searching for the earlier operation that established the receiver's relevant state. In E_A3_07_ScannerOutputStage, preview.setTiling(...) fails at line 59 because preview.setTilingMode(MODE_COPY_FROM_METADATA) at line 53 left its tiling state at startTiling. Intervening compression calls make that connection harder to spot.

Proposed first version

Track the source location of the call or construction that establishes a receiver's state in a particular @StateSet. Carry that origin through operations that preserve that state set. When a state error occurs, include a clickable “State established here” location only when the origin is unambiguous. Record the user-code call site after resolving the resulting state, rather than the location of the @StateRefinement declaration.

Start with straight-line code and a known resulting state. For the scanner example, the link should lead to line 53. If the origin cannot be established reliably, keep the current error without a link.

This needs verifier provenance metadata carried to the error DTO and an extension link to display it. Existing source mappings alone do not provide a reliable transition history. The feature is deterministic and does not require an LLM.

Acceptance criteria

  • Calls affecting another state set do not replace the tiling origin.
  • Two receivers, such as archive and preview, retain separate origins.
  • Constructor-established states can point to construction where applicable.
  • Branches with different possible origins, or transitions whose resulting state cannot be resolved reliably, do not produce a misleading single link.
  • Existing verification results remain unchanged.

Priority and scope

Lower priority, technically difficult enhancement. A conservative first version is preferable to guessing an origin in complex control flow.

Lenguaje dominante
Java
Estrellas
67
Forks
36
Merge medio
7 d 48 min
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de liquid-java/liquidjava

Todos los issues de liquid-java/liquidjava

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.