AS a developer, I want the ignore command to save to its own entity rather than a config string #406

New issue

Open

opened 2024-02-03 17:40:41 +00:00 by Vylpes · 0 comments

Vylpes commented

2024-02-03 17:40:41 +00:00

Owner

Epic:
Story Points:

SO THAT it is easier to maintain and edit

Acceptance Criteria

GIVEN I am a developer
WHEN I look in the database
THEN I will see all the ignored channels will be stored in its own entity instead

GIVEN I am a moderator
WHEN I ignore a channel
THEN the bot will save this to its own entity

GIVEN I am a moderator
WHEN I stop ignoring a channel
THEN the bot will remove this entity from the database

GIVEN I am a user
WHEN I type a message in a channel
THEN the bot will check if it has been ignored in the database entity
AND ignore actions if this the entity for this channel exists

Subtasks

Create IgnoredChannel entity
Update ignore command logic
Update ignore channel check logic
Update tests

Notes

No notes

Epic: \ Story Points: --- SO THAT it is easier to maintain and edit ## Acceptance Criteria GIVEN I am a developer WHEN I look in the database THEN I will see all the ignored channels will be stored in its own entity instead GIVEN I am a moderator WHEN I ignore a channel THEN the bot will save this to its own entity GIVEN I am a moderator WHEN I stop ignoring a channel THEN the bot will remove this entity from the database GIVEN I am a user WHEN I type a message in a channel THEN the bot will check if it has been ignored in the database entity AND ignore actions if this the entity for this channel exists ## Subtasks - [ ] Create IgnoredChannel entity - [ ] Update ignore command logic - [ ] Update ignore channel check logic - [ ] Update tests ## Notes *No notes*

Vylpes added the

labels 2024-02-03 17:40:53 +00:00

Vylpes added the

needs testing

label 2024-10-27 17:21:50 +00:00

Vylpes changed title from ~~Ignore command should save to config not its own entity~~ to AS a developer, I want the ignore command to save to its own entity rather than a config string

2024-12-01 14:34:26 +00:00

Vylpes removed the

needs criteria

label 2024-12-01 14:36:54 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: RabbitLabs/vylbot-app#406

No description provided.