Migrate to JDA 6

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #55 by @ReignBit — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
backend

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.

Description

enhancement

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)
Dominant language
Java
Stars
2
Forks
0
No merged PRs in 30d

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.

More from ReignBit/java-discord-kat

All issues in ReignBit/java-discord-kat

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.