-
Notifications
You must be signed in to change notification settings - Fork 1.2k
docs(debugger): add special vars section to expression language docs #28444
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
Conversation
Preview links (active after the
|
8fe8cc2 to
fb635d7
Compare
0b740b5 to
3ef3e39
Compare
3ef3e39 to
cd942bf
Compare
rtrieu
left a comment
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.
Minor feedback.
Co-authored-by: Thomas Watson <w@tson.dk>
rtrieu
left a comment
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.
Some minor edits for consistency and clarity.
Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
…28444) * docs(debugger): add special variables section to expression language docs * Update content/en/dynamic_instrumentation/expression-language.md Co-authored-by: Thomas Watson <w@tson.dk> * Apply suggestions from code review Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> --------- Co-authored-by: Thomas Watson <w@tson.dk> Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
What does this PR do? What is the motivation?
This pull request includes updates to the documentation for the Dynamic Instrumentation Expression Language. The changes introduce special variables for collection and dictionary operations, and improve clarity regarding their usage.
Documentation updates:
@it,@key,@value) for collection and dictionary operations, including descriptions and examples.Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes