TASEmulators / TASEmulators/BizHawk
[F.Rq.] Improve warning messages for malformed codes in cheatcode importer
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Cheats must be 13 characters long and not have spacing in front of code line.
Each Code must be on its own line example
816844A8 0000
816844AA 0000
817FFE00 3C0C
817FFE02 8080
luckily I am good at problem solving :D
Current warning message is too vague for average users.
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 at the cheatcode importer’s validation and warning-generation entry point, then reproduce malformed input using codes with incorrect length, leading spacing, or multiple codes on one line. Done means the importer reports which formatting rule was violated with a warning that is clear to average users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100