Is it supported to load datadog first and graphql second, as well as the other way around?

We already have tests like https://github.com/DataDog/dd-trace-rb/blob/master/spec/loading_spec.rb that start with a clean environment, given that this was a customer-reported issue I would consider adding a test that verifies that the reported case works correctly going forward.

Benchmarks

Benchmark execution time: 2024-08-05 18:32:43

Comparing candidate commit 6f6ce3e in PR branch vpellan/graphql-unified-tracer-require with baseline commit 4fbe269 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 10 metrics, 2 unstable metrics.

Is it supported to load datadog first and graphql second, as well as the other way around?

We already have tests like master/spec/loading_spec.rb that start with a clean environment, given that this was a customer-reported issue I would consider adding a test that verifies that the reported case works correctly going forward.

Hello! Thanks for the suggestions.
I've added a test that will require datadog first, then graphql, and the other way too.
I've also added a test for trace_with.

Codecov Report

❌ Patch coverage is 88.59060% with 17 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.86%. Comparing base (4fbe269) to head (6f6ce3e).
⚠️ Report is 5062 commits behind head on master.

@@            Coverage Diff             @@
##           master    #3813      +/-   ##
==========================================
- Coverage   97.87%   97.86%   -0.01%     
==========================================
  Files        1262     1263       +1     
  Lines       75653    75738      +85     
  Branches     3710     3719       +9     
==========================================
+ Hits        74044    74124      +80     
- Misses       1609     1614       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.