GitHub Enterprise GraphQL Schema needs to be considered before querying for new-ish fields
See original GitHub issueCopied from https://github.com/microsoft/vscode/pull/115940#issuecomment-854596119:
I can see the list of PRs but clicking on the dropdown shows nothing.
Extension output is as follows:
[Info] Failed to get pull request review comments: Error: GraphQL error: Field 'path' doesn't exist on type 'PullRequestReviewThread' GraphQL error: Field 'isOutdated' doesn't exist on type 'PullRequestReviewThread' [Info] Error: GraphQL error: Field 'viewerViewedState' doesn't exist on type 'PullRequestChangedFile' [Info] Failed to get pull request review comments: Error: GraphQL error: Field 'path' doesn't exist on type 'PullRequestReviewThread' GraphQL error: Field 'isOutdated' doesn't exist on type 'PullRequestReviewThread' [Info] Error: GraphQL error: Field 'viewerViewedState' doesn't exist on type 'PullRequestChangedFile' [Info] Failed to get pull request review comments: Error: GraphQL error: Field 'path' doesn't exist on type 'PullRequestReviewThread' GraphQL error: Field 'isOutdated' doesn't exist on type 'PullRequestReviewThread' [Info] Error: GraphQL error: Field 'viewerViewedState' doesn't exist on type 'PullRequestChangedFile'Github Authentification Output:
[Info - 09:22:45.590] Getting user info... [Info - 09:22:46.204] Got account info!Enterprise version is: v2.22.4
@kabel do you know why the above errors are happening? Is GHEP now out of sync with the extension again?
Copied from https://github.com/microsoft/vscode/pull/115940#issuecomment-854604614:
I had similar errors on our GHE instance. Based on the change log, these fields were introduced on 2020-09-23. I guess you have to upgrade the GHE to a version after that.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Introduction to GraphQL - GitHub Enterprise Server 3.5 Docs
A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client...
Read more >Queries - GitHub Docs
Every GraphQL schema has a root type for both queries and mutations. The query type defines GraphQL operations that retrieve data from the...
Read more >Objects - GitHub Docs
Objects in GraphQL represent the resources you can access. An object can contain a list of fields, which are specifically typed. For example,...
Read more >Style guide for the GraphQL schema - GitHub
This schema style guide summarizes how we design the GraphQL schema at Kiron ... The identifier field is owned by the API and...
Read more >howtographql/1-getting-started.md at main - GitHub
This schema only has a single root field, called info . When sending queries, mutations or subscriptions to a GraphQL API, these always...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Sadly, I have not had free time to explore this more and won’t have older GHE instances to work with. The recommendation remains to get current with the supported versions.
It’s only really feasible if we can decouple the interface features that rely on these object fields. Even that, I have not looked into.
Hi, is there any progress on this?
I met the same error here with Git Enterprise