Multigroup

[vq9o]

Changes

Forked from qbot/multi-group.

• Some sections have been entirely re-written such as deprecation/phase of previous addon & primary group for a better config & clean code.
• Code issue fixes
• Multi-group support
• queryString param "groupId" is required to be passed on API endpoints which touch a group. Example: promote, xp, etc.
• few more i prob forgo

[!CAUTION] In this new version of qbot, previous data of XP & suspensions will be lost due to new DB structure.

Tests

Legend

• ✅ = PASS BUG FREE/FULLY OPERATIONAL
• 🐛 = BUGGY
• ❌ = FAIL

Test results

• /joinrequest - ✅
• /acceptjoin - ✅
• /denyjoin - ✅
• /shout - ✅
• /promote - ✅
• /setrank - ✅
• /fire - ✅
• /roles - ✅
• /revertranks - ✅
• /groupban - ✅
• /ungroupban - ✅
• /exile - ✅
• Info commands - ✅

[!CAUTION] XP & Suspension system un-tested.

Status

STABLE: YES

Contributors:

• vq9o
• yogurtsyum

[yogurtsyum]

Can you document what these changes actually do?

[yogurtsyum]

I'm not sure what the first two bullet points under Changes mean. The third is not new--at least, it shouldn't be. This PR should be merged into my multigroup branch with just what you intended to make different, not be the PR for all of multi-group support into master in the first place.

As for the last bullet point, everything that changes needs to be mentioned in the PR so I know exactly what it is I am accepting--for both documentation purposes and quality assurance.

I think what you should do is resubmit this PR to LengoLabs:multigroup with a title that accurately describes what is different that you added (like permissions, if that's the main goal here). You should write a description that exhaustively covers everything changed, and document how it changes how people should use the bot. (It looks like there was a lot of stylistic changes to my code... why?)

That was a lot, so let me (Lengo) know if you have any questions on the Discord.