Description 📹

Enhance the /starky-connect command by displaying a "Reconnect {networkName}" button for each network when the user has already linked a Starknet wallet on all networks. Also, fix the logic of alreadyConnectedOnBothNetworks to support multiple networks from configs/networks.json.

Proposed Actions 🛠️

Here’s a checklist of actions to follow for resolving this issue:

1. Fork and Create Branch:
   Fork the repository and create a new branch using the issue number:

   git checkout -b fix-[issue-number]

2. Update the alreadyConnectedOnBothNetworks logic:

   • Modify the logic to check across multiple networks instead of assuming only two.
   • Ensure that it dynamically checks the number of configured networks in configs/networks.json rather than a hardcoded value.

3. Modify the response when a user is already connected on all networks:

   • Instead of just displaying the message:
     "You have already linked a Starknet wallet to this Discord server on both networks. Use /starky-disconnect first if you want to link a new one",
     dynamically generate a message that accounts for all available networks.
   • Add "Reconnect {networkName}" buttons for each network.

4. Implement UI components for the buttons:

   • Utilize ActionRowBuilder and ButtonBuilder to create buttons dynamically for each network.
   • Each button should allow users to reconnect to the specific network.

5. Ensure proper error handling and logging:

   • Update logging to provide better insights in case of unexpected behavior.
   • Handle edge cases where network configurations might change.

6. Run Tests and Commit Changes:
   Make sure your changes don't break existing functionality and commit with a clear message:

   git commit -m "Fix: Display reconnect buttons and update multi-network support"

Required 📋

To keep our workflow smooth, please make sure you follow these guidelines:

• Assignment: Don't create a pull request if you weren’t assigned to this issue.
• Timeframe: Complete the task within 3 business days.
• Closing the Issue: In your PR description, close the issue by writing Close #[issue_id].
• Review Process:
  • Once you've submitted your PR, change the label to "ready for review".
  • If changes are requested, address them and then update the label back to "ready for review" once done.
• Testing: Test your PR locally before pushing, and verify that tests and build are working after pushing.

Thank you for your contribution 🙏

⚠️ WARNING: Failure to follow the requirements above may result in being added to the OnlyDust blacklist, affecting your ability to receive future rewards.