intent: a roll-up where: cannot test a column for null - value: null is refused at parse though Criteria.eq is null-safe
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 56/100
Línea de trabajo
Start at the parser check that raises “has no value” for roll-up where conditions; the issue identifies the shared ScheduleConditionIntent path and says ScheduleSupport.valueReading, JavaLiterals, and Criteria already handle null. Trace how eq and ne conditions reach Criteria, then check the generated output for value: null. Done means the sample intent generates and null equality and inequality render as is null and is not null; the broader reversal behavior is optional.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happens (14.95.0)
A roll-up where: (#7542) cannot test a column for null. The parser refuses value: null:
rollups:
- { name: paymentPosted, entity: JournalEntry, via: CustomerPayment, field: postedEntries,
where: [{ field: Status, op: eq, value: POSTED }, { field: Storno, op: eq, value: null }, { field: ReversedBy, op: eq, value: null }] }
POST /services/ide/intent/generate answers 422 with rollup [paymentPosted] where-condition on [Storno] has no value.
The rest of the chain already handles null:
ScheduleSupport.valueReadingemits{kind: "null"};JavaLiteralsrenders it asnull;Criteria.eq(property, null)is null-safe and rendersproperty is null, andne(property, null)rendersis not null.
Only the parse-time check blocks it. A filter on a nullable to-one ("not a reversal", "not reversed", "no parent yet") therefore has no declarative form. Every other operator excludes NULL under SQL three-valued logic, so there is no workaround inside where:.
Case
BusinessIntents/base-journal#101. The posted-entry roll-ups onto a source document (customer and supplier payment, depreciation, disposal, cash order) must not count a red-storno twin made by reversals: (#7886). The twin carries the same back-reference, so the reversed source shows postedEntries 2 and stays frozen for good, while the ledger has already netted it to zero. The module ships an interim: five hand-written listeners instead of the five roll-ups.
Ask
- Accept
value: nullwithop: eq/op: nein a roll-upwhere:(and inschedules[].where/items: where:, which shareScheduleConditionIntent). It rendersis null/is not null, asCriteriaalready does. - Optional, for the full reversal semantics: a one-hop term such as
ReversedBy.Status != POSTED. With it, the source stays counted while its reversal is still DRAFT or was rejected, the same reading #7950 asks forrefuse:.
Acceptance
The roll-up above generates. After a POSTED entry is reversed and its twin is posted, the parent's count drops from 1 to 0, with no hand-written handler.
Related: #7542 (roll-up where:), #7905 (coalesced roll-ups drop a member's where:), #7942 (a status-filtered roll-up does not recompute on a transition), #7950 (reversal refuse terms are record-local).
🤖 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la 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 eclipse-dirigible/dirigible
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
eclipse-dirigible/dirigible#7958 ·
Los mantenedores suelen responder en 1 día
-
intent: a create-from without fromStatus answers 200 on a missing or unknown source id (no 400/404)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
eclipse-dirigible/dirigible#7945 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
eclipse-dirigible/dirigible#7891 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
eclipse-dirigible/dirigible#6538 ·
Los mantenedores suelen responder en 1 día
-
Create shortcut for Camel filesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
eclipse-dirigible/dirigible#4812 ·
Los mantenedores suelen responder en 1 día
Todos los issues de eclipse-dirigible/dirigible
Issues similares
-
approved
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
checkstyle/checkstyle#22129 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
objectionary/lints#1577 ·
Los mantenedores suelen responder en 2 días
-
ChaosEngine: backup-remote doctor row passes while consumer mode hides bot memory from gitPosiblemente ocupada @MohabMohie la tomó hoy. Abiertoagentic
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ShaftHQ/SHAFT_ENGINE#7263 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100