You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, Tracer Provider isn't fully typed and documented. We need to complete subsegment context manager typing, and any critical typing from X-Ray SDK that's worth bringing for a Tracing Provider.
Since these might change in the future due to OTel support, we should focus on key features only.
Why is this needed?
As of now, autocomplete isn't fully working for escape hatch features. We don't need to provide all types in X-Ray SDK, but main features that we also make use of, like subsegments and context manager.
fromaws_lambda_powertoolsimportLogger, Tracertracer.provider# should no longer be Any
Summary
As of now, Tracer Provider isn't fully typed and documented. We need to complete subsegment context manager typing, and any critical typing from X-Ray SDK that's worth bringing for a Tracing Provider.
Since these might change in the future due to OTel support, we should focus on key features only.
Why is this needed?
As of now, autocomplete isn't fully working for escape hatch features. We don't need to provide all types in X-Ray SDK, but main features that we also make use of, like subsegments and context manager.
Which area does this relate to?
Tracer
Solution
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: