WorldconVotingSystems / WorldconVotingSystems/nomnom

improve UX around claiming codes, to help users work with the fact that codes are a limited resources

Open
#442 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17
Forks
15
Avg merge
11m
Merged PRs (30d)
1

Description

Because game codes are a limited resource and users know that, it might be worth making some improvements to give users somewhat more accurate information about game code availability. I recommend the following fixes:

  • Right now, if a user already has a code for a game, and returns to the Display Code page later, they have to click "Claim code" again to see their code. (And if they're wrong that they already have a code, e.g. if they clicked on the wrong architecture, clicking that button will allocate a new code.) It would be better to tell the user they already have a code when they go to Display Code in the first place.
  • Right now, if no codes are available, the "Claim code" button still appears. It would be better to tell the user that no codes are available, rather than make them decide whether to click the button and only then tell them. (I know there's a race condition here, but i think it's okay to ignore it - it's okay if occasionally a user clicks the button and is told that codes just ran out, but the typical case should be giving the user the accurate information.)
  • If code acquisition failed because no codes were available, don't show the user the "This code is unique to you. You can access it again at any time by returning to this page" message.

Contributor guide

No contributing guide indexed for this repository

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 at the Display Code page and trace the Claim code flow, including the no-codes-available response. The work is done when users with an existing code see it immediately, users are told when no codes are available before claiming, and the unique-code message is omitted after an unsuccessful acquisition.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.