-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reimplementing bots #119
Reimplementing bots #119
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couln't find any missing newlines 😞
packages/backend/src/controllers/connectors/plugins/discordBot.class.ts
Outdated
Show resolved
Hide resolved
packages/backend/src/controllers/connectors/plugins/discordBot.class.ts
Outdated
Show resolved
Hide resolved
Thank you for your review! @p-fruck @antonplagemann What happen if a user has no security key ? Hopefully this should not be a thing. Because many computers nowadays have a TPM that is used e.g. for Windows Hello and even all modern Smartphones can handle FIDO2. The status board is currently empty because it can not handle the new response. But this in scope of the next user story (I should start to write them down instead of keeping them in mind 😅) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fantastic 🔥 👍 😊
Description
This PR is linked to #116. I have implemented a new
connectorService
which handles the publishing of new notifications or update connectors. If no connector is stored in the database, the .env-vars will be used to create a new connector. This can be used to setup and use the service without visiting the dashboard. Now it is possible to add further connector plugins like email, slack, matrix or webhooks.In was not possible to refactor existing endpoints to the new implementation. Therefore I will do/fix this in separated user stories, because that would be to much for a single user story. The following problems are address in the user stories:
Another topic are unit tests: Unfortunately it was not possible to find a great solution to test an abstract class without rewriting tests again and again (for further plugins). So I skipped all tests that are effected by that.
Types of changes
Checklist
[ ] Make sure you are requesting to main. Don't request to release branch!