feat(client-stats): expose css obfuscation param#225
Conversation
and temporarily point libdatadog to the current rev APMSP-2969
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3818d7c14
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| libdd-common = { version = "3.0.1", default-features = false } | ||
| libdd-tinybytes = { version = "1.1.0", default-features = false } | ||
| libdd-library-config = { version = "1.1.0", default-features = false } | ||
| libdd-capabilities-impl = { git = "https://github.com/DataDog/libdatadog",rev = "c7131222cb42dd0513821456a4071245c4a819f6", default-features = false } |
There was a problem hiding this comment.
When packaging or publishing datadog-opentelemetry, these workspace dependencies are inherited by the crate and Cargo treats git-only normal dependencies as non-publishable. The Cargo Book states crates.io does not allow dependencies on code outside crates.io, and the supported fallback is to specify both git and version so local builds use git while published crates use the registry version. Without version entries here, any release/package step will be blocked until these dependencies are rewritten.
Useful? React with 👍 / 👎.
1 participant
What does this PR do?
Expose the experimental client side stats obfuscation for internal testing/benchmarking.
Motivation
What inspired you to submit this pull request?
Additional Notes
TODO:
APMSP-2969