liquidvotingio / liquidvotingio/api
Explore voting closure
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
While looking at updating voting results on updates done to global delegations (#44, #52), the issue of post-voting results updates came up.
We need a lightweight way to freeze voting results so they don't change after the fact.
A possible solution might be added a `closed` flag to the `results` table. A more involved solution would be having the higher concept of a `Voting`, with timed periods and such, but if possible we'd like to keep lean and leave that to the consumer platform to define.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the context from global delegations in issues #44 and #52, then inspect how voting results are represented in the results table. The issue needs a decided lightweight approach for freezing results and clear acceptance criteria before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100