Add test output fields to GraphQL API#3520
Merged
josephsnyder merged 1 commit intoKitware:masterfrom Mar 10, 2026
Merged
Conversation
This commit continues our ongoing effort to expose all CDash data via GraphQL. These new `path`, `command`, and `output` fields are not currently filterable because they are pulled from a separate relation. In the future, we can create a Postgres view which joins these relations and a corresponding model to allow these fields to be filtered.
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.
This commit continues our ongoing effort to expose all CDash data via GraphQL. These new
path,command, andoutputfields are not currently filterable because they are pulled from a separate relation. In the future, we can create a Postgres view which joins these relations and a corresponding model to allow these fields to be filtered.