Skip to content

fix: Make sure "other" answers are correctly handled - #1764

Merged
Chartman123 merged 1 commit into
mainfrom
fix/submit-other
Oct 27, 2023
Merged

fix: Make sure "other" answers are correctly handled#1764
Chartman123 merged 1 commit into
mainfrom
fix/submit-other

Conversation

@susnux

Copy link
Copy Markdown
Collaborator

In the backend it handling the "other" answer setting was not changed after switching from object to array for extra settings.

In the frontend the value handling of the checkboxes or radio switches was not correct as the initial values is always an empty array. This lead to issues with radio switch answers.

@susnuxsusnux added bug Something isn't working 3. to review Waiting for reviews labels Oct 26, 2023
@Chartman123Chartman123 added this to the 3.4 milestone Oct 26, 2023

@Chartman123Chartman123 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code wise this looks good :) I'll test it in the evening on my local instance

@Chartman123

Chartman123 commented Oct 26, 2023

Copy link
Copy Markdown
Collaborator

@susnux Could you please have another look at ResultsSummary.vue? For radio questions there is a separate line now for each custom value. They should be aggregated under "other" like for checkboxes.

My bad... I had entered one of the available values into the other field and that's why it was counted to the predefined option.

@codecov

codecovBot commented Oct 26, 2023

Copy link
Copy Markdown

Codecov Report

Merging #1764 (8303476) into main (6d74165) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files
@@ Coverage Diff @@## main #1764 +/- ##
=========================================
Coverage 42.98% 42.98% Complexity 614 614 =========================================
Files 58 58 Lines 2489 2489 =========================================
Hits 1070 1070 Misses 1419 1419 

In the backend it handling the "other" answer setting was not changed
after switching from object to array for extra settings.
In the frontend the value handling of the checkboxes or radio switches
was not correct as the initial values is always an empty array.
This lead to issues with radio switch answers.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@Chartman123
Chartman123 merged commit 3f870b0 into mainOct 27, 2023
@Chartman123
Chartman123 deleted the fix/submit-other branch October 27, 2023 07:40
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to reviewWaiting for reviewsbugSomething isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@susnux@Chartman123