max-mapper / max-mapper/requirebin

Expose server-side processes in the UI

Open
#64 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
389
Forks
73
PR merge metrics
No merged PRs in 30d

Description

Roughly 50% of the time, RequireBin just hangs and the 'loading' animation at the top right carries on forever. It'd be good to get some feedback on what was going on during this time (asynchronous feedback messaging), because otherwise the only diagnosis the user can make is that RequireBin just doesn't work a lot of the time.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the UI's top-right loading animation and the server-side request path that can leave it running indefinitely. Define which asynchronous progress or status messages users should see during these waits; the work is done when a stalled or slow RequireBin process provides useful feedback instead of only appearing hung.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.