hasura / hasura/graphql-engine
json parse error on console when connecting to local v3 engine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Steps to reproduce:
1. Sign out of hasura console
2. follow steps 1-3 listed on page [Create a supergraph](https://hasura.io/docs/3.0/getting-started/build/init-supergraph/)
3. Opening the link in step 3(https://console.hasura.io/local/graphql?url=http://localhost:3000) given on the above page redirects you to login page. After successful login, you're redirected to the console, which then throws the json parse error.
https://github.com/user-attachments/assets/afb84d70-5c88-4adf-b9a6-da7a6592d60e
browser console logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by following the Create a supergraph steps and opening the local GraphQL console URL after signing in. Start with the browser console logs shown in the report; done means the console loads the local v3 engine without a JSON parse error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100