Skip to content
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

chore | Add graphQL description to span exclusion rules APIs #237

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

AnandShivansh
Copy link
Contributor

Description

Please include a summary of the change, motivation and context.

Testing

Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested helm chart locally.

Checklist:

  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been merged and published in downstream modules

Documentation

Make sure that you have documented corresponding changes in this repository or hypertrace docs repo if required.

@AnandShivansh AnandShivansh requested a review from a team as a code owner June 18, 2024 19:10
Copy link

github-actions bot commented Jun 18, 2024

Test Results

25 tests  ±0   25 ✅ ±0   23s ⏱️ -4s
11 suites ±0    0 💤 ±0 
11 files   ±0    0 ❌ ±0 

Results for commit a3b21be. ± Comparison against base commit a09a60f.

♻️ This comment has been updated with latest results.

@GraphQLNonNull
boolean disabled();

@GraphQLField
@GraphQLName(RULE_TYPE_KEY)
@GraphQLDescription(
"Exclude span rule type tells us whether it is user configured rule or system rule")
// TODO: make this field non-nullable
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a change we still want to make? Anything stopping us from doing it? It can't be done once the API is exposed as it'll be a breaking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants