Closed CarsonF closed 1 month ago
Ah this doesn't work because it forces all subclasses to conform to this delete
signature.
We still want subclasses to be able to change that as this is just a builder/helper class.
I'm not going to go through the effort of implementing the omit
logic here, which is how we got around this on the EdgeDB side.
DtoRepo.delete
to replacedeleteNode
This query is specific to the resource type of the class, which is safer (assumes less) than any type. It also matches the EdgeDB version so migration should be seamless.Now you can
throw e
or skipcatch
all together if there's no other logic.