hasura / hasura/graphql-engine

v2.0.0-alpha.5-cloud.2 UI JSON parsing error for table permissions

Open
#6,702 1 comment 0 reactions 0 assignees View on GitHub
c/console
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

Version: `v2.0.0-alpha.5-cloud.2`

**Issue**
Going through backend course, I'm unable to continue because of JSON parsing errors during setup of user permissions.

**Steps to reproduce**
1. Deploy newest `v2.0.0-alpha.5-cloud.2` to cloud
2. Create `user` table
3. Create new role
4. In new role settings, select "Without Any Custom Checks" or "With Custom Checks"
5. Experience error in console and inability to move forward

**Expectation**
- Ability to apply permissions to new role

**Details**
Heroku deployment, tutorial based error experienced on this step:
https://hasura.io/learn/graphql/hasura/authorization/2-users-table-permissions/

Unable to continue adding permissions to a table img
![image](https://user-images.githubusercontent.com/7892158/112161790-7569a300-8bb9-11eb-9cbe-ba6948ddf1a6.png)

```
0vendor.js.gz:1 Uncaught SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse ()
at e (vendor.js.gz:1)
at e (vendor.js.gz:1)
at e (vendor.js.gz:1)
at e (vendor.js.gz:1)
at g (vendor.js.gz:1)
at main.js.gz:1
at vendor.js.gz:1
at vendor.js.gz:1
at e (vendor.js.gz:1)
e @ vendor.js.gz:1
e @ vendor.js.gz:1
e @ vendor.js.gz:1
e @ vendor.js.gz:1
g @ vendor.js.gz:1
(anonymous) @ main.js.gz:1
(anonymous) @ vendor.js.gz:1
(anonymous) @ vendor.js.gz:1
e @ vendor.js.gz:1
l @ vendor.js.gz:1
h @ vendor.js.gz:1
m @ vendor.js.gz:1
A @ vendor.js.gz:1
N @ vendor.js.gz:1
O @ vendor.js.gz:1
I @ vendor.js.gz:1
Lr @ vendor.js.gz:1
tl @ vendor.js.gz:1
He @ vendor.js.gz:1
jr @ vendor.js.gz:1
(anonymous) @ vendor.js.gz:1
t.unstable_runWithPriority @ vendor.js.gz:1
nl @ vendor.js.gz:1
Pr @ vendor.js.gz:1
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.