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

Fix wrong result when "Result options" with "String result" setting enabled #2275

Merged
merged 3 commits into from
Mar 17, 2023

Conversation

xispa
Copy link
Member

@xispa xispa commented Mar 17, 2023

Description of the issue/feature this PR addresses

This Pull Request fixes an issue introduced with #2259 that makes the system to display the result option value (instead of the text) for analyses that have "Result options" properly configured, but with the "String results" setting enabled as well.

With this Pull Request, system gives priority to the fact that the analysis has "Result option" values properly configured over the "String results" setting.

Current behavior before PR

After the result is submitted for an analysis with result options and "String results" setting enabled, the system displays the value of the selected option:

Captura de 2023-03-17 09-30-56

Desired behavior after PR is merged

After the result is submitted for an analysis with result options and "String results" setting enabled, the system displays the text of the selected option:

Captura de 2023-03-17 09-30-29

--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.

@xispa xispa added the Bug 🐞 label Mar 17, 2023
@xispa xispa requested a review from ramonski March 17, 2023 08:37
@ramonski ramonski merged commit e943081 into 2.x Mar 17, 2023
@ramonski ramonski deleted the fix-result-options-string branch March 17, 2023 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants