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

print: a reprint of an issued document cannot say it is a copy - no first-print / copy flag in the print data (BG ОРИГИНАЛ / КОПИЕ)

Abierto
  • ¿Algo no está bien?
#7,908 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
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
api, backend

Línea de trabajo

Start by tracing the live Print endpoint, POST /services/print/<Entity>, and the Snapshot function mentioned in the report; compare their print data flow to determine where render state or a request flag could be exposed to templates. The issue offers two possible approaches but leaves the behavior and design to choose. Done means a template can distinguish an original from a copy for the relevant print flows.

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

Descripción

What happens

A BG paper invoice must carry ОРИГИНАЛ on its first print and КОПИЕ on every print after that (ППЗДДС чл. 78 ал. 1 т. 2; copies are not numbered; the e-mailed PDF is always an original). A .print template can only print what the data gives it, and on v14.88.0 (and v14.90.0) neither the document page's Print (POST /services/print/<Entity>?lang=..&template=.. with the feeder's payload) nor the snapshot mint passes anything that says whether this render is the first one. The print-template catalogue (#7755 / PR #7763) versions templates, not renders, and the <Doc>Copy snapshot rows (function: Snapshot) record the issue-time mint but are not consulted by the live Print.

So the module can print ОРИГИНАЛ always (BusinessIntents base-sales-invoices#74 does) but never КОПИЕ (base-sales-invoices#80).

Ask

One of:

  1. A render flag in the print data: {{print.copy}} (boolean) - false for the snapshot mint and for the first live Print of a record, true once the record has been printed/minted before - so a template writes <if source="print.copy"><text>КОПИЕ</text></if> and the reverse for ОРИГИНАЛ. The record's snapshot child (function: Snapshot) is a natural "has it been rendered" source.
  2. Or: a Print -> Original / Copy choice on the document page, passing a copy=true request flag the template can read (the reviewer accepted "two explicit print buttons" as most BG systems do).

Filed from BusinessIntents base-sales-invoices#80 (pre-train wave 2026-10-17); the module keeps #80 open on this.

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.