Notification settings

[Marchand-Nicolas]

Description 📹

Create a new slash command /starky-notifications-settings that allows administrators to configure notification preferences. This command should display a menu to:

• Set or edit the Discord channel where notifications will be sent.

• Select the types of notifications to send:

  • User getting new role
  • User connecting wallet
  • User losing role

Additionally, implement a new database table to store these settings.
(for context, in the next issue it will be used to send notifications in the specified channel when a user is updated)

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. Implement Changes:

• Create a new table in the database to store notification settings per server/guild.

  • Fields: guild_id, notification_channel_id, notify_role_added, notify_wallet_connected, notify_role_removed

• Implement the /starky-notifications-settings command.

• Display a menu with:

  • A dropdown or channel selector to choose the notification channel.
  • Checkboxes or toggles for each notification type.

• Save or update the selected preferences in the database upon submission.

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

git commit -m "Fix: Add /starky-notifications-settings command with DB 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.

[MingZoox]

Hi there @Marchand-Nicolas, I'm a fellow experienced blockchain developer and I’d love to work on this issue!

I’ve already run successful the bot locally and read through the project. You've provided a clear and detailed issue description, and I’ll follow it closely to deliver a solid implementation.

Once assigned, I’ll get started right away. Thanks!

[JamesVictor-O]

Hello @Marchand-Nicolas I'm a frontend and smart contract developer with expertise in Cairo, Solidity, TypeScript, and JavaScript, with confidence in my ability to deliver high-quality work. With experience in frameworks like Next.js, React.js, and Tailwind CSS, and a strong background in open-source contributions (particularly in the Starknet and Stellar ecosystems), I'm well-equipped to take on this challenge. As a fellow in the OnlyDust Fellowship Program, I've not only contributed to various projects but also gained experience maintaining projects on OnlyDust, which has given me valuable insight into the platform and its workflows. @Marchand-Nicolas i would really love to work on this issue.

Recommended by OnlyDust for high-quality and dependable contributions.

[emarc99]

Would love to do this!

[brisstone]

Hy team! I would like to tackle this. Kindly assign.