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
Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.
2. A failing test has been provided
3. A local solution has been provided
4. A pull request is pending review
Describe the bug
The endpoint in the .meshrc.yaml file does not get environment variables interpolated, causing Websocket / Websocket legacy requests to fail where the URL is specified in this way. The URL is interpolated correctly when doing schema fetching and for non-subscription queries, but does not get interpolated before being passed to the websocket drivers (both legacy WS and WS), causing requests to fail.
To Reproduce Steps to reproduce the behavior:
Use an environment variable to specify the GraphQL handler endpoint
Try to subscribe to data.
The issue applies both when using a single endpoint and when using a dedicated subscriptionEndpoint.
Expected behavior
Should be interpolated correctly with environment variables and other tokens, and allow this.
Additional context
Was the root problem that led to me reporting #5402
The text was updated successfully, but these errors were encountered:
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
Github,
Stackblitz
or
CodeSandbox
Describe the bug
The endpoint in the
.meshrc.yaml
file does not get environment variables interpolated, causing Websocket / Websocket legacy requests to fail where the URL is specified in this way. The URL is interpolated correctly when doing schema fetching and for non-subscription queries, but does not get interpolated before being passed to the websocket drivers (both legacy WS and WS), causing requests to fail.To Reproduce Steps to reproduce the behavior:
The issue applies both when using a single
endpoint
and when using a dedicatedsubscriptionEndpoint
.Expected behavior
Should be interpolated correctly with environment variables and other tokens, and allow this.
Additional context
Was the root problem that led to me reporting #5402
The text was updated successfully, but these errors were encountered: