Backend pass through problems

Cerrado
#45 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@arlange ya está trabajando en esto.

Desde el 29/10/2026.

  • #395 de @arlange — fusionado

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Problem

The setup service will return a structured problems list with its build errors (vitruv-tools/Methodologist-SetupService, structured-errors issue).

The backend currently keeps only a text summary: SetupServiceApiHandler.describeError turns the response into [errorCode] message, and the asynchronous build stores only a string as the error message. The structure is lost before it reaches the frontend.

Proposal

  1. Parse problems in SetupServiceApiHandler and carry it in SetupServiceException.
  2. Return it in the backend's error response for the synchronous download endpoints:
    • /v1/vsums/{id}/build/artifact
    • /v1/vsums/{id}/build/bundle
    • /v1/vsums/{id}/project
  3. Store the problems as JSON on the asynchronous VsumBuild and return them from GET /v1/vsums/{id}/builds/{buildId}.
  4. Map the upload names back to the platform's own files (e.g. reaction file ID and name), so the frontend can open the right editor.
  5. Keep the infrastructure/input distinction: setup-service 503 → backend 502/503, setup-service 422 → backend 400 with problems.

Acceptance criteria

  • A rejected build returns the setup service's problems unchanged, with platform file IDs added, on both the synchronous and asynchronous paths.
  • Older setup-service responses without problems still produce the current text message.
Lenguaje dominante
Java
Estrellas
0
Forks
0
Merge medio
8 h 5 min
PR fusionados (30 d)
15

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 vitruv-tools/Methodologist-SetupService

Todos los issues de vitruv-tools/Methodologist-SetupService

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.