google/comprehensive-rust

Keep state of the Rust Playgrounds when navigating between slides

Open

#1,476 opened on Nov 13, 2023

View on GitHub
 (31 comments) (0 reactions) (1 assignee)Rust (32,954 stars) (2,009 forks)batch import
enhancementgood first issue

Description

Today, the embedded Playgrounds are reset when you navigate between slides. This has caused problems: if people navigate away from a slide to look something up, they've suddenly lost their work.

This is actually the reason why we don't make the exercises editable directly in the slides: too many people have lost work because of this.

We should be able to store the current state in the browser's local storage.

Contributor guide

Tech stack
rustjavascripthtmlcss
Domain
frontenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptlocalStorageslide navigation code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
The issue requires storing the state of embedded Rust playgrounds across slide transitions. Investigate the current slide navigation mechanism, likely in the frontend code (HTML/JS). Look for where playgrounds are instantiated and how they reset. Implement preserving state using the browser's localStorage API. Check if there are any existing utility functions for state persistence. Consider handling both saving and restoring playground state, and possibly clearing state when the user explicitly resets or the session ends.