devHenrik123 / devHenrik123/Klaval
WPM roles
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Description:**
Implement optional wpm roles, that can be enabled during the setup. It must be disabled by default.
The wpm roles represent the users current klavia wpm.
The role will be assigned after verifying and linking a klavia account.
The wpm role will be updated through the sync command and therefore also sync every 30 minutes during the scheduled update of all server users.
These are the required roles:
- 0 - 19 WPM
- 20 - 39 WPM
- 40 - 59 WPM
- 60 - 79 WPM
- 80 - 99 WPM
- 100 - 119 WPM
- 120 - 139 WPM
- 140 - 159 WPM
- 160 - 179 WPM
- 180+ WPM
If the setting has been enabled for the server, the required roles shall automatically be created, if not already present.
**Tasks:**
Therefore all of the things below need to be implemented:
- [ ] Initialization of WPM roles (during setup or scheduled?)
- [ ] Per server setting in persistence file
- [ ] Option during setup command
- [ ] Synchronization of WPM roles during sync command & scheduled trigger
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the setup command, sync command, persistence file, and scheduled update flow mentioned in the issue. Trace how per-server settings and linked Klavia accounts are handled, then verify that enabling the option creates the ten roles and that sync updates assignments both manually and on the scheduled run; disabled servers should remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100