Consider adding troubleshooting hints to playground
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
Related to #861
There are a number of issues that can occur in the playground that may cause problems:
- Service worker out of date.
- Extensions interfering with playground.
- SW disabled in dev tools so things stop working when you open dev tools.
Most of these shouldn't be that hard for folks to figure out (in theory) but it'd be nice to have a list of things to try that was easily accessible from the UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the playground UI and the related issue #861 to understand the existing context. Identify where troubleshooting guidance can be made easily accessible, and consider the listed service-worker and browser-extension problems covered when the hints are available from the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100