-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Catch permission errors #2290
Conversation
Removed vultr server and associated DNS entries |
20d6842
to
10a0b6a
Compare
10a0b6a
to
9f57d40
Compare
@@ -45,14 +48,40 @@ const publicHttpLink = createHttpLink({ | |||
headers: { "x-hasura-role": "public" }, | |||
}); | |||
|
|||
const errorLink = onError(({ graphQLErrors }) => { | |||
const handlePermissionErrors = (message: string, operation: Operation) => { | |||
const permissionErrors = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a number of issues on the Hasura graphql-engine
repo requesting better error messages - please see explanation here for context hasura/graphql-engine#6716 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like Vultr is still reporting global deploy delays, but code looks good here & works for me locally following same steps in your demo !
Thanks for checking that - having issue after issue with Vultr yesterday! |
What does this PR do?
Demo
In the video below, I removed my
platformAdmin
role and unhid the "create flow" button to test what this would look like.Screen.Recording.2023-10-09.at.20.17.36.mov