After some discussion with the Azure CDAs, it was decided that then Task.thenXXX(...) methods should be removed to 1) simplify the API surface area and 2) avoid confusion with Java developers that have experience with similarly named APIs in the CompletableFuture class. None of the primary orchestration patterns require these methods, so it's generally safe to remove them.
As part of this work, we should also remove the comparison with CompletableFuture in the class's JavaDoc documentation. This is to help further prevent confusion through comparison.
After some discussion with the Azure CDAs, it was decided that then
Task.thenXXX(...)methods should be removed to 1) simplify the API surface area and 2) avoid confusion with Java developers that have experience with similarly named APIs in the CompletableFuture class. None of the primary orchestration patterns require these methods, so it's generally safe to remove them.As part of this work, we should also remove the comparison with CompletableFuture in the class's JavaDoc documentation. This is to help further prevent confusion through comparison.