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
I created the browser extension Go Ground2Space [Source-code]. The extension automatically opens the equivalent go play-space url instead of a given go-playground url.
(Note that, for now, it only supports chrome/edge but there are plans for supporting other popular browsers in future)
This extension is targeted mainly at people who are frequent or exclusive users of go play-space (instead of go-playground). It is convenient for them since, whenever they click on a random playground link somewhere (or someone shares one with them), they can rest assured that it will open up with syntax highlighting goodness!
I thought that it might be useful for such users to know that such an extension exists. Would you consider noting the existence of the extension somewhere on your repo or readme?
The text was updated successfully, but these errors were encountered:
somombo
changed the title
Consider mentioning redirection browser extension
Consider mentioning go play-space browser extension on readme
Nov 5, 2020
Hello, shameless plug here 😌.
I created the browser extension Go Ground2Space [Source-code]. The extension automatically opens the equivalent go play-space url instead of a given go-playground url.
(Note that, for now, it only supports chrome/edge but there are plans for supporting other popular browsers in future)
This extension is targeted mainly at people who are frequent or exclusive users of go play-space (instead of go-playground). It is convenient for them since, whenever they click on a random playground link somewhere (or someone shares one with them), they can rest assured that it will open up with syntax highlighting goodness!
I thought that it might be useful for such users to know that such an extension exists. Would you consider noting the existence of the extension somewhere on your repo or readme?
The text was updated successfully, but these errors were encountered: