Ability to clear tutorial-project association

[jcandan]

Is your feature request related to a problem? Please describe.

To run a CodeRoad tutorial, When I open an empty folder in VS Code, And I choose a tutorial and hit Start, successfully spinning up the first lesson, And I close and later re-open that project in VS Code, Then it presents the lesson that was chosen.

There is no way to go back and pick a different tutorial.json file.

Even If I delete that folder, and recreate a new one with the same name, I am kicked into the previously chosen tutorial.

Only if I create a new folder with a different name am I able to pick a different tutorial.json.

Describe the solution you'd like

It seems that I should be able to back out of a lesson and pick a different tutorial. However, I could see that workflow being problematic if the directory is not empty.

At the very least, if I delete a project folder, the screen to choose a different tutorial should come up. Perhaps sensing that the folder is empty, the ability to go back a pick a different tutorial becomes enabled.

This sensing may want to consider the case of an existing git directory, as noted in #629.

Describe alternatives you've considered

This is not only a user experience concern, but also a storage concern. It seems the project folder path association with a tutorial is stored or cached.

This (may be unrelated) also creates a problem for contributors. When they want to hit F5 to spin up an empty project it automatically selects the last project worked on. The only way to start over is to delete the project folder that was last used.

Does this get cleared at any point?

Additional context

See #626 for the current work-around I have to do to get to the first lesson on a local environment.

[jcandan]

Also, we may want to note in the documentation how one can open an empty folder in a workspace.

I have to admit, though I use VS Code daily, I struggled to understand how to do this: 😆

• Open a new VS Code window
• Put a single empty folder in the workspace

So, we might consider changing this to:

• Open a new VS Code window
• Put a single empty folder in the workspace via File > Add Folder to Workspace...

/docs/docs/create-a-practice-tutorial.md

I personally ended up using:

mkdir empty-dir1
code empty-dir1

mkdir empty-dir2
code empty-dir2

Having to do this constantly until this feature enhancement is made.