-
Notifications
You must be signed in to change notification settings - Fork 43
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: Filter (all, active, past, future) DB support for sigma dao #732
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.
Let's change the proposals filter and naming (please also adopt in UI):
- ongoing = (what you have as active): proposals that are in voting right now
- active = proposals which are ongoing + future proposals
I've made code suggestions in the SQL for that, so you can just accept them.
Co-authored-by: Robert Zaremba <[email protected]>
Co-authored-by: Robert Zaremba <[email protected]>
Co-authored-by: Robert Zaremba <[email protected]>
Co-authored-by: Robert Zaremba <[email protected]>
Co-authored-by: Robert Zaremba <[email protected]>
@robert-zaremba This PR is ready for 2nd review. |
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.
pre-approving, before merging make sure to add foreign key as noted in the comment
Co-authored-by: Robert Zaremba <[email protected]>
No description provided.