Skip to content

Conversation

linusha
Copy link
Collaborator

@linusha linusha commented Sep 24, 2025

This implements a basic amendment frontend, similar to what we had in the old version.

All logic is handled in the frontend. This is not a problem for now, but will need to change once we want to polish this.

It looks like this (only if a vote has amendments):

image image

The amendment page itself:
image


What I think would be nice: At least information about the authors and the outcome of an amendment vote directly on the amendment page itself. We cannot really give a lot of insights on an amendment right now, as we can make no statements about the contents. Thus, I think these two things could provide enough information to decide which amendment one wants to google. (Thinking out loud for a second, we could linkt to the text quite easily however I believe? Maybe directly on this page already and once more on the page of the amendment itself?). We could also think about showing small bars so that one can easily see which ones were close, as these might be of special interest.
All of this would however require to get more information than that currently available in related.


As usual, open to any design suggestions regarding how stuff looks.

The following cases are handled:

1. A vote is a main vote and has amendments -> amendment UI on ShowVotePage is shown.
2. A vote is not a main vote but /amendments is browsed -> 404
3. A vote is a main vote without amendments and /amendments is browsed -> 404
I am not sure why this is necessary in the first place, or rather, something goes wrong here. I checked both with `typeof` and both are strings, but the types say one is a number.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant