8000 Issue with auto launching / continuing a tutorial · Issue #33 · freeCodeCamp/CodeAlly-CodeRoad-freeCodeCamp · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Apr 16, 2024. It is now read-only.
This repository was archived by the owner on Apr 16, 2024. It is now read-only.
Issue with auto launching / continuing a tutorial #33
@moT01

Description

@moT01

I was having an issue loading CodeRoad (0.17.2, but this issue probably started at 0.16.0 or 0.17.0) in the docker container we have set up to run tutorials locally. Basically, I would launch CodeRoad and it would auto load my last tutorial, and none of the files were there to continue the tutorial. And there was no way to start over - not even by rebuilding the container, strangely. I know we need something like this to work for continuing tutorials, and perhaps this will work on CodeAlly. I dug into it a little bit to try and figure out how it works - CR is using some kind of local storage in VS Code to save some sort of state or tutorial or something. And I think it may write something to a file as a second way to save the state - or maybe it only does that. Not sure exactly, but it's something along those lines.

I see three methods at the moment for running tutorials

  1. Locally, without docker (I really never use this method)
    Current behavior:
    -I open a workspace, start a tutorial
    -If I open the same workspace, it will continue the tutorial where I left off (auto load)
    -I can start new tutorial by creating a new workspace

    Not that big of an issue here. I can't start a different tutorial within a workspace - I have to create a new one. If a workspace breaks - maybe I delete the files or something, it's pretty much stuck.

  2. Locally, with docker (using the rdb-alpha repo)
    Current behavior:
    Similar to the above, except the container always loads the same workspace. So if it breaks, it's pretty stuck.

    It's not an immediate issue. I pinned the container to use 0.15.1 for now, so it doesn't auto load the tutorials. We could probably just leave it like that if we have to.

  3. CodeAlly
    Not sure exactly how it will work on CodeAlly. Does each container (tutorial) have its own workspace? That could potentially work - I can see people getting stuck if they delete the files there. There is a plan do have a CodeAlly dashboard where users can delete the containers I believe, so there would be that fallback.

I'm not sure what the solution is. Maybe we need some way for users to clear the storage? Or a way to truly start over if someone gets stuck - maybe a pop-up when continuing a tutorial, "Do you want to continue where you left off?" I know there already is something like that when running local tutorials. I don't see a clear solution that would work for all these methods at the moment. I'll keep pondering, maybe something will come.

Metadata

Metadata

Assignees

Labels

CodeRoadPriority: HighBasically, can't launch without a fixPriority: MediumShould probably fix, but might be able to launch without

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0