codecombat / codecombat/codecombat
purchased.gems is NaN often
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.6k
- Forks
- 4.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 39
Description
It's probably related to payments code, and can cause user saving problems.
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
Start by locating the payments code and references to purchased.gems. Investigate when the value becomes NaN and whether that coincides with user saves. Done means purchased.gems remains a valid numeric value during saving.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100