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

intent: a roll-up status: without statusWhenPartial (or statusWhenFull) generates uncompilable Java - the whole app 404s

Abierto
#7,941 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Read IntentParser and trace how it validates the roll-up status configuration; compare that with GlueIntentGenerator and RollupAggregates.appendStatus. Start by running the existing RollupAggregatesTest and identify coverage for only one of statusWhenFull and statusWhenPartial being set. Done means this configuration is rejected with the missing key named, or status emission handles the missing value, with a regression test confirming the behavior.

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

Descripción

Problem

A sum roll-up that declares status: + statusWhenFull: but no statusWhenPartial: (or the reverse) passes the parser and generates Java that does not compile. Because one javac task compiles the whole client-Java batch, every controller of the app 404s, not just the roll-up.

Where (release commit 862f6d1a, 14.93.0)

  • GlueIntentGenerator writes the missing key as "": base.put("statusWhenPartial", withStatus && rollup.getStatusWhenPartial() != null ? ... : "") (GlueIntentGenerator.java ~L705-710).
  • RollupAggregates.appendStatus splices it in verbatim: java.util.Objects.equals(parent.Status, ) and parent.Status = sum.compareTo(capacity) >= 0 ? 7 : ; (RollupAggregates.java L186-L215). The same file already guards capacityField / balanceField with strOrEmpty for exactly this reason. The status pair has no such guard.
  • IntentParser checks only that status: is a to-one relation of the parent. It never requires both statusWhenFull and statusWhenPartial.
  • RollupAggregatesTest covers both-set and both-empty, but not one set with the other missing.

Expected

Either the parser refuses status: without both statusWhenFull and statusWhenPartial (naming the missing key), or the emission treats a missing one as "leave the status alone in that band". The refusal is the smaller fix.

Found on 14.88.0 by BusinessIntents (wave 2026-10-17, base-fixed-assets / base-cash-desk) and re-checked against the 14.93.0 source; still present.

🤖 Generated with Claude Code

Lenguaje dominante
Java
Estrellas
278
Forks
97
Merge medio
19 h 30 min
PR fusionados (30 d)
242

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 eclipse-dirigible/dirigible

Todos los issues de eclipse-dirigible/dirigible

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.