-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add note about Datadog.configure
requiring block in 1.x to Upgrade Guide
#1970
Add note about Datadog.configure
requiring block in 1.x to Upgrade Guide
#1970
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@delner any concerns about this change? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really see this particular change as constructive or useful. It calls out a weird usage that was employed as a hack as if it's meant to be used this way.
I wouldn't recommend this. If the hack was predicated by some flaw, it would be better to address that flaw.
@delner Since this is something that changed (and even bit us!) it seems nice to have it documented as a change in the "Breaking Changes" section -- it is an actual breaking change in the public API. But I do agree that by itself, calling
we suggest:
|
…Guide Spotted this change when working with @lloeki on validating 1.0.0.beta2.
82b0347
to
ce9017b
Compare
Updated PR with the advice to remove such uses. |
Codecov Report
@@ Coverage Diff @@
## master #1970 +/- ##
==========================================
+ Coverage 97.53% 97.69% +0.15%
==========================================
Files 998 1001 +3
Lines 49006 50453 +1447
==========================================
+ Hits 47800 49291 +1491
+ Misses 1206 1162 -44
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've used this pattern before, specially when trying to run the host application test with ddtrace
enabled.
I spoke with David a week back and he was happy with the alternative advice; merging this in. |
Spotted this change when working with @lloeki on validating 1.0.0.beta2.