You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm running into a very similar issue as the one described here #204
I can query just fine but as soon as I try to execute a mutation: it fails.
I've tried setting a bearer token through .env as well as in nuxt.config. I've also tried setting a specific (admin) bearer header with codegenHeaders but no luck.
What's weird is I can execute the mutation just fine in a graphql external client (insomnia), so that tells me my token and permissions are probably fine.
What's nerve racking is that when I allow anyone (public role) to execute mutation: it succeeds.
Directus logs: Schema is not configured to execute mutation operation.
which usually mean the request was made with insufficient rights.
Expected behaviour
The mutation should succeed with the bearer token set for the default client or with the one set in codegenHeaders
Environment
Darwin
v16.19.0
3.2.0
2.2.1
[email protected]
vite
app
,modules
,graphql-client
[email protected]
-
9.22.3
Describe the bug
Hello,
I'm running into a very similar issue as the one described here #204
I can query just fine but as soon as I try to execute a mutation: it fails.
I've tried setting a bearer token through
.env
as well as in nuxt.config. I've also tried setting a specific (admin) bearer header withcodegenHeaders
but no luck.What's weird is I can execute the mutation just fine in a graphql external client (insomnia), so that tells me my token and permissions are probably fine.
What's nerve racking is that when I allow anyone (public role) to execute mutation: it succeeds.
Directus logs:
Schema is not configured to execute mutation operation.
which usually mean the request was made with insufficient rights.
Expected behaviour
The mutation should succeed with the bearer token set for the default client or with the one set in
codegenHeaders
Reproduction
No response
Additional context
I can provide a private reproduction if needed!
I had to downgrade node from 18.14 to 16.19 because of this codegen bug #295
Logs
No response
The text was updated successfully, but these errors were encountered: