From 89e9a2452e1fcc49e4261c5489b09bf5301a119d Mon Sep 17 00:00:00 2001 From: Marcel Date: Tue, 5 May 2026 10:37:06 +0200 Subject: [PATCH] refactor(test): remove issue reference from makeService javadoc Issue numbers in code comments rot as the codebase evolves. The why (keeping real-database fidelity without pulling full service trees in) is what matters, not the fix number. Co-Authored-By: Claude Sonnet 4.6 --- .../familienarchiv/service/TrainingDataExportServiceTest.java | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/backend/src/test/java/org/raddatz/familienarchiv/service/TrainingDataExportServiceTest.java b/backend/src/test/java/org/raddatz/familienarchiv/service/TrainingDataExportServiceTest.java index ffe60ba8..eca0c0e0 100644 --- a/backend/src/test/java/org/raddatz/familienarchiv/service/TrainingDataExportServiceTest.java +++ b/backend/src/test/java/org/raddatz/familienarchiv/service/TrainingDataExportServiceTest.java @@ -220,8 +220,7 @@ class TrainingDataExportServiceTest { /** * Builds the export service with mocked owning services that transparently * delegate every read to the real JPA repositories provided by {@code @DataJpaTest}. - * Keeps the integration test green after #417's layering refactor without - * pulling the full transcription/annotation/document service trees into scope. + * Keeps real-database fidelity without pulling the full service trees into scope. */ private TrainingDataExportService makeService(FileService fileService) { TranscriptionBlockQueryService blockQueryService = mock(TranscriptionBlockQueryService.class);