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
One issue we have that negatively impacts developer experience is that requests to Playground don't show up in the Network tab of the browser's developer tools. This makes debugging tasks and day-to-day development considerably harder than a traditional frontend-backend scenario.
The reason why requests to playground don't show is because we're not technically making a request, we're just calling a function in PlaygroundClient.
The text was updated successfully, but these errors were encountered:
Once way to do this could be to have a service worker act as a proxy between the extension and Playground. To issue a request to Playground, we would instead issue it to a proxy URL (e.g. /playground-proxy) using fetch(). The /playground-proxy would call the request() function of PlaygroundClient and return the response.
Something that might prevent this from being feasible is that we would not have the instance of PlaygroundClient in the service worker, I guess.
One issue we have that negatively impacts developer experience is that requests to Playground don't show up in the Network tab of the browser's developer tools. This makes debugging tasks and day-to-day development considerably harder than a traditional frontend-backend scenario.
The reason why requests to playground don't show is because we're not technically making a request, we're just calling a function in
PlaygroundClient
.The text was updated successfully, but these errors were encountered: