Skip to content
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

Frontend: A few design fixes #215

Closed
wants to merge 51 commits into from
Closed

Frontend: A few design fixes #215

wants to merge 51 commits into from

Conversation

Lionqueen94
Copy link
Contributor

@Lionqueen94 Lionqueen94 commented Aug 5, 2024

Done:

Fixed from #101 :

  • when a list has exactly n*25 candidates, the spacer/separator for the next 25 candidates is shown. The separator should only be added if there is a (n*25)+1'nd candidate. Scherm­afbeelding 2024-08-01 om 11 13 17
  • The zebra-striping of the rows does not match the striping used in the paper forms. On paper, the first row of each 25 rows is white. In our digital form, row 26 and row 76 have a dark background. Each block of 25 rows should start with a white background.
    Scherm­afbeelding 2024-08-05 om 09 49 33

Lionqueen94 and others added 30 commits July 18, 2024 17:59
… not validated when voters_recounts is filled in
Lionqueen94 and others added 18 commits July 30, 2024 18:43
…ences-fields-to-api-including-validation' into 110-backend-add-recounted-differences-fields-to-api-including-validation

# Conflicts:
#	frontend/app/component/form/voters_and_votes/VotersAndVotesForm.test.tsx
Improve testability of `PollingStationFormController` children by
allowing default values to be passed to the controller. This can then
be used to set `recounted: true` to test validation logic of the
recounted fields.
…nted-differences-fields-to-api-including-validation
@praseodym
Copy link
Contributor

It looks like this PR includes some unintended changes (e.g. to the backend) that might be the result of incorrectly resolved merge conflicts?

@Lionqueen94
Copy link
Contributor Author

It looks like this PR includes some unintended changes (e.g. to the backend) that might be the result of incorrectly resolved merge conflicts?

Ah shit I created this from my other branch, will correct it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants