magefree / magefree/mage

CardUtil should be broken into separate smaller util files

Open
#13,886 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

refactoring
Dominant language
Java
Stars
2.4k
Forks
940
Avg merge
2d 12h
Merged PRs (30d)
160

Description

CardUtil has gotten bloated over time and really should be broken apart into smaller classes like TextUtil and StreamUtil and such. This isn't hard to do, but the only thing keeping me from doing it already is that it may cause conflicts with current unmerged PRs. I just wanted to open this to track it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating CardUtil and inventorying the responsibilities it currently combines, including the proposed TextUtil and StreamUtil areas. Check whether current unmerged pull requests touch the same code before choosing the split; done means the utility responsibilities are separated into smaller classes without disrupting existing users.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.