-
Notifications
You must be signed in to change notification settings - Fork 12
Description
EDIT: On further thought, I want to change the scope of this issue to "vote comment UI". I think it still makes sense to accept comments as a form of feedback even if we don't publish them. The rest of this issue is still relevant to that narrower scope.
This was (somewhat haphazardly) thrown into the API spec, but let's put a pin in it. In light of the hidden complexity here I think it's best to mark this as a "nice to have" and swing back around to it. Further discovery uncovered the following implications to consider:
- Listing/paginating votes
With just a numeric value, votes are simple to aggregate and display; they can be totaled either server-side or client-side and displayed in aggregate with a simple numeric affordance. Adding comments necessitates an entirely new UI for listing and displaying those comments—each of which would require it's own affordance.
- Deciding what to display (and how to model it in the API)
Are comments displayed on their own, or alongside individual vote values? Do comments have a unique endpoint, or are they coupled with the proposals endpoints? How do individual vote values factor in?
- Anonymity
Displaying individual user votes has implications for the system as a whole, possibly influencing vote outcomes. This would need to be discussed at a higher level.