ReignBit / ReignBit/java-discord-kat
Migrate to JDA 6
Open
Nobody has claimed this yet.
- #55 by @ReignBit — closed without merging
enhancement
- Dominant language
- Java
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I have not updated the JDA version in a long time, in which a lot of breaking changes have been made. I should look at updating to JDA 6.
- Investigate the changes needed for the migration
- Refactor for the update
- Use this time to potentially expand on how we currently handle Models/ActionRows (esp. for music track queuing)
Contributor guide
No contributing guide indexed for this repository
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 JDA dependency and reviewing the JDA 6 breaking changes. Then inspect the current Models/ActionRows handling, especially music track queuing, and assess the migration work described here. Done means the project is updated to JDA 6, the required refactors are complete, and the existing behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100