-
-
Notifications
You must be signed in to change notification settings - Fork 63
Standup endpoint #11
Comments
I have a question that would help with this. Specifically with the information from the discord bot. How would we get the standup from it? Is it something from discord.js or do we need to use the Discord API? |
Oh I see so we could just send the information from EddieBot to the API using Is thus the kind of system you are talking about? |
yes that is correct - sorry if I explained it badly, thank you for challenging 👍 - I will update the description |
Thanks for helping me to understand. 😄 |
I think, perhaps we could simplify this and avoid using discord API? |
Yep 👍 the bot will send the data to our API which will store the data in the db |
This is a suggestion. If you think of anything better please let us know. We could have a variable in the Then in the API we modify the Please share your suggestions. 😄 👍 |
Yep the API url in the Bot and UI will be part of the config, as this will change depending if we are developing locally or in production etc. Yep, the |
This question might be a bit redundand. Does the |
It only sends the message in the channel it is called in |
Oh .... Do you also know if there is any way to get the sender through discord.js? Something like |
|
Nice 👍 , yes we will need to send the user with the standup message - so we can save the standup message against the user Currently the Discord user API is being created, so we can move things to the API |
I could do this.
|
Thanks @Cahllagerfeld 👍 . Good question, I do not think we need a |
* feat: ✨ Standup Module Init Standup Module * test: Update Unittest & Lint * refactor: Remonve preneded I from interface * test: E2E Testing Standupmodule * test: Added new Step-definition * refactor: Turn Search Endpoint to Get Request + Added Tests * style: Consistent naming for Scenarios + Blank Lines between Functions
PR merged |
It would be great to encourage more daily standup information.
Update after discussion with @mstanciu552 below
The text was updated successfully, but these errors were encountered: