playground version history

[lambtron]

would be cool to go back to a previously saved/deployed version of the code in the playground.

[vwkd]

Maybe a playground could be backed by a internal Git repo just like projects can be backed by a user-owned Git repo on GitHub.

Essentially the difference between a playground and a repo would be that Deploy takes over the work to setup the repo, hook it up to deploy, and provides an online editor to write the code, so the user doesn’t need to touch GitHub.

Playground could become a seemless online experience to deploy small amounts of JavaScript that don‘t require the management of GitHub. For example, one could write one‘s own IFTTT / Zapier functions to automate one‘s existence on the Web.

Also could make the Deploy internals simpler by having a Git repo as the single source of code and only different ways to get that repo, like internal for playgrounds, GitHub for user projects, or even an URL for repos anywhere on the Web.

But building a Web IDE that works on all platforms is not trivial and requires constant maintenance. Consider outsourcing the editor altogether to a third party services like CodeSandbox as this complexity is likely not a problem Deno Deploy wants to solve. The Web IDE would modify the Git repo and Deno Deploy would take it from there to deployment.