Michael Staib
Michael Staib
https://github.com/ChilliCream/graphql-platform/pull/6769
Can you open a PR with a snapshot test? Once the PR is there. I can help fix it.
As a workaround you can override the module name with the ModuleInfo ....
This issue is on the backlog and will soon picked. The release horizon will be 14.1
You need to put the token on the init request .... The authorization header is not supported in browser when using websocket. I will post how to do it later.
@TheJemy191 exactly ... on the server you need `SocketAuthorizationInterceptor` we used to have a full demo ... but we need to have another look at that.
The documentation is outdated. Out of the box you only have `AUTH_NOT_AUTHORIZED`. While the internal policy provider still could differentiate between those we cannot get that information from the policy...
This actually is a wrong assumption. When we talk about known error, or lets say domain errors. Things that are expected with stage 6a then you do not report it...
Hey there, sorry for the late answer. I will do a video on how to set this up properly, there are a couple of questions around this. For instance... How...
We do not allow PRs against version 13 branches ... all changes have to go against `main`. We can cherrypick it to 13 once it went through the main branch.