Better return values for concept cluster/pipeline deletion method

Onto-Med / top-backend

Spring Boot based backend of the TOP Framework

MIT License

0 stars 1 forks source link

Better return values for concept cluster/pipeline deletion method #214

Open fmatthies opened 4 months ago

fmatthies commented 4 months ago

The following two deletion methods both return a ResponseEntity<void>:

ConceptPipelineApiDelegateImpl.deleteConceptPipelineById
ConceptClusterApiDelegateImpl.deleteConceptClustersForPipelineId

Maybe it's more feasible to change this to a ResponseEntity<PipelineResponse>; this would need a change in top-api as well, as those methods are overrides.

fmatthies commented 4 months ago

For deleteConceptPipelineById one could also think about an option to only partially delete (or better pick up where failed previously because there are already steps present) The second option could/should be checked in top-frontend startPipeline.