This is feedback from the Azure SDK team. The primary feedback is that only "entry point" or "front door" classes, like DurableTaskGrpcClient and DurableTaskGrpcWorker should have builders. We should avoid them for other "non-entry point" classes, based on UX research done over the past 10 years or so.
Builders can be replaced with constructors, getters, and setters. We can still support the fluent code style by having setters return the current object.
Builders to be replaced currently live in the following classes:
This is feedback from the Azure SDK team. The primary feedback is that only "entry point" or "front door" classes, like
DurableTaskGrpcClientandDurableTaskGrpcWorkershould have builders. We should avoid them for other "non-entry point" classes, based on UX research done over the past 10 years or so.Builders can be replaced with constructors, getters, and setters. We can still support the fluent code style by having setters return the current object.
Builders to be replaced currently live in the following classes: