-
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
73 #87
73 #87
Conversation
@l3r8yJ thank you for your Pull Request. I'll assign someone to review it soon. If this PR solves a |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #87 +/- ##
=============================================
- Coverage 80.89% 57.65% -23.25%
Complexity 32 32
=============================================
Files 10 12 +2
Lines 89 111 +22
Branches 2 1 -1
=============================================
- Hits 72 64 -8
- Misses 17 47 +30
☔ View full report in Codecov by Sentry. |
@h1alexbel please review this Pull Request. Deadline (when it should be merged or closed) is You should check if the requirements have been implemented (partially or in full), if there are unit tests covering the changes and if the CI build passes. Feel free to reject the PR or ask for changes if it's too big or not clear enough. Estimation here is |
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.
@l3r8yJ take a look at my comments, please
* Chat id command. | ||
*/ | ||
@Component("/chatid") | ||
public class ChatId implements 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.
@l3r8yJ maybe a better name for this class will be RegisterChat?
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.
@h1alexbel Honestly, I'd rather make this command like /unsubscribe
because we already have /register
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.
@l3r8yJ we don't have register chat id command.
We have registry, but it's a different flow
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.
@h1alexbel I think you can get by with a registry, storing the chat id
+ token
at the same time
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.
@l3r8yJ you can, but still now we have a separate flow for it, simply because register chat is like user registration in blamer, while register token is actually different flow
What do you think?
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.
@h1alexbel honestly, I don't see any cases where a user would want to save a chat without receiving notifications
what's the motivation behind it?
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.
@l3r8yJ actually yes, agree.
So we will reduce amount of commands simply to: /unsub and /token. On token we will validate if the chat already exists in db
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.
@l3r8yJ can you apply these changes to diagrams in order to sync up?
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.
@h1alexbel i'll create a puzzle
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.
Ok
@h1alexbel take a look, please |
@h1alexbel Don't forget to close this ticket before the deadline (2023-09-12T20:18:59). You are past the first half of the allowed period. |
@h1alexbel take a look, please |
@l3r8yJ commented on mixing flows |
@h1alexbel thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard. |
closes #73
PR-Codex overview
This PR focuses on making several changes to the codebase. The notable changes include:
Registry.java
andRegistryTest.java
filesanswers.properties
file to update thetoken
andregistry
propertiescactoos
andeasy-random-core
in thepom.xml
fileStart.java
file to useMono
from Reactorpackage-info.java
fileConversation.java
interface to useMono
from ReactorUnsubscribe.java
file to handle the/chatid
commandTokenOf.java
fileTokenOf
class