We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The start_time is documented as having requiring a type of Integer here: https://github.com/DataDog/dd-trace-rb/blob/master/docs/GettingStarted.md#manual-instrumentation, however it is handled as a Time here:
start_time
Integer
dd-trace-rb/lib/ddtrace/span.rb
Line 423 in 409ec65
Passing as an integer causes error on the nsec field request.
nsec
I think the docs should be updated to note the correct type.
The text was updated successfully, but these errors were encountered:
Fix Tracer#trace start_time type documentation
24299dc
Fixes #1264 This PR updates the required type for the `Datadog::Tracer#trace(start_time:)` option. The type required is a Ruby [Time](https://ruby-doc.org/stdlib-2.7.2/libdoc/time/rdoc/Time.html) object, while the documentation erroneously requested an `Integer`. As as follow up, I suggest we move most of this documentation to our published API docs: https://www.rubydoc.info/github/DataDog/dd-trace-rb/Datadog/Tracer#trace-instance_method. This allows us to keep the documentation close to implementation, and prevent information drift between the two.
Fix Tracer#trace start_time type documentation (#1268)
9a8a383
Successfully merging a pull request may close this issue.
The
start_time
is documented as having requiring a type ofInteger
here: https://github.com/DataDog/dd-trace-rb/blob/master/docs/GettingStarted.md#manual-instrumentation, however it is handled as a Time here:dd-trace-rb/lib/ddtrace/span.rb
Line 423 in 409ec65
Passing as an integer causes error on the
nsec
field request.I think the docs should be updated to note the correct type.
The text was updated successfully, but these errors were encountered: