-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/cli #54
Feature/cli #54
Conversation
* separate actions into commands * leave the daemon as as another command
out of curiosity, what are some of the race conditions? |
@nramirez I've created the following issue for the refactor #58. I think it's going to require changing quite a few things for this, for example, to pass the discord client around. One of the race conditions is that sometimes when the client initializes and we immediately call the discord APIs that have the .channel, it wouldn't grab anything and would raise an exception instead. |
That race condition won't happen if you call the client like this => 996ea55#diff-fda8f0e13abe3d5c5685ad895fa528dd6067c41b66b6ebc6d1de71ca9a704d8dR55 I agree you can refactor later, but given that my changes now landed you can rebase and reuse the new builder. |
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.
LGTM, sure thing we can improve this in the next follow-ups.
I would recommend rebasing to avoid the dup with the client creation.
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.
Agree with Naz's comments, well done!
There's a few race conditions, but I've done the minimum required for everything function.
This is how the interface looks:
I've tested everything. All working