GeneralMagicio / GeneralMagicio/pw-frontend

Super low priority, for version 2 - Instead of editing manually the results, come up with a solution that will allow the user to go back and make more pairwise assessments

Open
#185 1 comment 0 reactions 0 assignees View on GitHub
question
Dominant language
TypeScript
Stars
16
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Editing manually right now makes it so the user can't go back and play our fun game.

This is a tragedy.

We need to make their manual edits happen in another way... there are dozens of solutions, but the most obvious would be to allow the user to Boost or Slash a project and just letting them add some OP to that project, then that boost/slash could stay there on the side and the pairwise "score" could also stay on the other side and if a user wants to do more assessments, they are adjusting the pairwise score, but the boost/slash remains.

In every solution there are a lot of details to work out... (like where does the boost come from?) but the end goal is clear.... people should be able to continue playing the pairwise game!

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named in the issue, so begin by tracing where manual result edits and pairwise assessments are handled. Done means users can continue the pairwise game after making edits, while any Boost or Slash adjustment remains separate from the pairwise score.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.