-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Manage proposal status consistently #1984
Comments
@taoeffect Are we planning to create messages in the general chatroom for the status changes of all the proposals?
|
@Silver-IT Sure, yes I think that would be helpful 👍 |
@taoeffect, Yeah. If we notify proposal status in several ways, in relative the users would not miss to vote proposals. But now, we notify the proposal status using notifications.
Do we need to notify using general chatroom too? What I think is that we should notify the proposal status in one way, IMHO it's using notification, not using general chatroom. So, I would like to change workflow and make it to create notification instead of creating message when proposal is expiring. And I remember you asked me for what we use |
Go for it 👍 |
Problem
Now, we have two types of constants which represent the proposal state.
One is the list of these variables which have prefix of
STATUS_
.And the other is
PROPOSAL_VARIANTS
enum.Solution
Use only one constant, and remove the other.
The text was updated successfully, but these errors were encountered: