Deprecate and then remove old propagation model
lukemelia opened this issue · 0 comments
lukemelia commented
#63 introduced a new way to handle propagation and it was opt-in for compatibility reasons.
We should consolidate back to a single approach by:
- Add a deprecation warning for when the service's
isPropagationEnabled
is false and update the docs - In the next major version, remove the flag and now-unused code.