Add additional fields to GraphQL Build type #2098
Merged
Conversation
This file contains 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
williamjallen
force-pushed
the
graphql-build-type
branch
from
17c380c
to
3bb071e
Compare
williamjallen
force-pushed
the
graphql-build-type
branch
from
3bb071e
to
d2deb87
Compare
williamjallen
force-pushed
the
graphql-build-type
branch
from
d2deb87
to
147bcfa
Compare
williamjallen
force-pushed
the
graphql-build-type
branch
2 times, most recently
from
4bfdbe5
to
baf22fb
Compare
zackgalbreath
force-pushed
the
graphql-build-type
branch
from
baf22fb
to
d8dcae6
Compare
williamjallen
force-pushed
the
graphql-build-type
branch
from
d8dcae6
to
395794f
Compare
zackgalbreath
approved these changes
Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The new GraphQL API is the highlight feature in the upcoming CDash 3.4 release, but we don't currently expose much information via the new API. This PR fills in some of the gaps by adding GraphQL fields for most of the columns in the
buildtable.Although this PR is straightforward from a functionality perspective, I am looking for in-depth feedback during the code review process, particularly related to the field names, types, and documentation. In some cases, the documentation I added is sparse because I was not able to determine the precise purpose of some columns.