EAR-2439 mutually exclusive logic not applied when mutually exclusive answer has only one option

[sanjeevz3009]

What is the context of this PR?

Mutually exclusive logic is not applied when a mutually exclusive answer has only one option.

JIRA ticket: https://jira.ons.gov.uk/browse/EAR-2439

Credit to @Farhanam76 for helping me understand the Author product, giving me the context of the Author product, and the codebase, coming up with the initial logic to solve this issue and letting me work on this ticket with her.

Bug

Reproduce for reviews

• Design a question, have a textarea answer, then have a mutually exclusive answer (OR answer field in Author) and have only one answer option for the mutually exclusive.
• Add the routing logic rule of Match OneOf and select the exclusive answer (OR answer) option.
• Then select a page to go to if the exclusive answer checkbox is ticked.
• Else go to the end of the current section.

When you do this currently, there is a bug where if you enter something in the textarea, it will go to the end of the current section page as it should. If you tick the checkbox, it should go to the page configured in the routing logic rule but currently, it doesn't and goes to the end of the current section page (the bug).

This is not an issue if there are multiple answer options for the exclusive answer (OR answer) as it'll become radio buttons instead of a checkbox (happens when you only have one answer option for the exclusive answer field).

What to do after everything is green

1. • Bring this branch up-to-date with Origin/Master
2. • If there are a lot of commits or some are not helpful to read, squash them down
3. • Click the Merge button on this pull request
4. • Does this change mean the Capability examples questionnaire should be updated?
5. • Move the Jira ticket for this task into the next stage of the process

Fix

• File changed: src/eq_schema/builders/routing2/newRoutingDestination/index.js
• Nested if statement added under if (condition === "OneOf") to check if the answer object contains type:"MutuallyExclusive" and if the options length === 1
  • If the above conditions are met AllOf passed into routingConditionConversion instead of OneOf to fix this bug.
• Created a new file called utils/functions/answerGetters.js and it has a reusable function called getAnswerById to retrieve the answer object by using the answer ID.