Something weird I noticed: AbstractEncapsulateFieldCommandHandler disables cancellation, but still uses cancellation token after that.
Some audit is required.
First - why exactly it disables cancellation? No other similar refactoring command handlers disable it.
Second - if disabling cancellation is required, we should not use cancellation token that will never be cancelled.
Something weird I noticed: AbstractEncapsulateFieldCommandHandler disables cancellation, but still uses cancellation token after that.
Some audit is required.
First - why exactly it disables cancellation? No other similar refactoring command handlers disable it.
Second - if disabling cancellation is required, we should not use cancellation token that will never be cancelled.