After transfer process, the new regular user still has a "0" quota
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 61
- Forks
- 34
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 22
Description
After transfer process, the new regular user still has a "0" quota, which IMO doesn't make sense (because all regular users should have a real quota, unless they are guests).
Unless it's deliberate, I think it would be relevant to automatically apply the “default quota” to the user after conversion.
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
The issue does not name a file, entry point, or test. Trace the transfer or guest-to-regular-user conversion flow and where the default quota is assigned, then check how a converted user retains a quota of "0". Done means a converted regular user receives the default quota while guest users remain unaffected, with coverage for the conversion behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100