Uploaded image for project: 'VS Code Extension'
  1. VS Code Extension
  2. VSCODE-360

Refreshing VSCode with an unsaved playground results in empty files

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: 0.10.0
    • Component/s: Playgrounds
    • Labels:
      None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • Not Needed
    • Up for triaging

      We should either keep these files around unsaved when the workspace is reopened or at least cleanup these untitled files so they aren't shown and folks down have to close them.

      Reproduction:

      1. Create a new playground (without saving).
      2. Refresh VSCode (cmd+r)
      3. Note the `Untitled` empty file

      Reported on github: 
      https://github.com/mongodb-js/vscode/issues/466 

            Assignee:
            Unassigned Unassigned
            Reporter:
            rhys.howell@mongodb.com Rhys Howell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: