Different results from GraphQL Explorer on Web vs. GraphQL API in Postman #57968
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I recently discovered the GraphQL API Explorer on web and have been working on a search query that seems to give me the results I expect.
However, upon taking the same query into Postman and posting my query to https://api.github.com/graphql, I only ever get a single result rather than the 201 results I get from the web explorer above (which sends the queries to https://graphql.github.com/graphql/proxy if that matters.) The query cursor also returns that there are no further pages. The single result I get is always associated with the same author among the five in my query.
For the latter, I have tried both classic and fine-grained personal access tokens (read access to administration, code, commit statuses, discussions, issues, merge queues, metadata, pages, and pull requests).
Should I expect the same results from both endpoints, or is this expected behaviour? Are there configuration settings or search parameters that I've overlooked?
My query follows:
And variables:
Beta Was this translation helpful? Give feedback.
All reactions