[datadog_dashboard] Refactor Formula Query#2829
Open
Conversation
ecdatadog
changed the title
fpighi
approved these changes
Mar 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Similarly to schema and HTTP=>State function that are already centralized , the State Function => HTTP object was not factorised and code was duplicated and not always the same .
I am doing that for coherence but I don't know if it was on purpose as some pairs (Widget / Query Type) could be impossible. In this case, we should modify the schema or note that some pairs are incompatibles.
I am also preparing this PR as I would like we review if all the Query is properly managed currently