fix(headless): advanced search queries parameters are not passed along

[ThibautNazare]

SVCC-4986

Bug Description

On Wednesday, April 9th, we received a message about a customer having issues with the search page. The generated answer was returning citations that should be filtered out. They open a discuss with details.

A similar search page as the setup by the customer but using facets filtering was provided to us to reproduce the issue but we were unable to reproduce it.

After meeting with customers and observing the behaviour, we discovered that the customer was leveraging the cq advance search queries parameter to be able to filter results displayed to user, based on a value set in the user session.

Root cause search

Based on the fact that searches were not returning valid results only when an answerConfigurationId was set in the search page, we started by making sure that the answerAPI was handling correctly this advanced search query parameter. Once that was validated, we moved up the chain and made sure in headless that this parameter was transmitted to AnswerAPI in the generated request. There, we found out that not only cq parameter was not passed along to the request, but also that the aq, dq and lq advanced search query parameters were not passed along.

Solution

Even though the customer is only using cq, we decided to pass along all advanced search queries parameters to the API.

Tests & Example page updated

Unit test mock and expected payload have been updated. I also updated the example genqa page so that we have an example of how-to activate those parameters nearby.

How to test locally

• Make sure your local setup is ready to build and run atomic
• Pull this branch
• Run headless unit tests with the following command npx nx run headless:test
• Edit packages/atomic/dev/examples/genqa.html file to add a answerConfirgurationId(fc581be0-6e61-4039-ab26-a3f2f52f308f) as a property in the component at line 124
• Run atomic dev with this command npx nx run atomic:dev
• Open your local browser to this page
• Open your developer tool and then Network tab
• Look for a /generate request
• You should find that the parameters in the request like in the following screenshot

[developer-experience-bot]

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

Live demo links

• Storybook

• Playwright report

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	248.6	248.8	0.1
commerce	361	361.1	0
search	419.6	419.8	0
insight	410.8	410.9	0
recommendation	259.5	259.6	0
ssr	413.4	413.5	0
ssr-commerce	377.5	377.6	0

[louis-bompart]

For the scope of this PR; the state "fishing" should be done in the selector.
At large, the whole constructAnswerQueryParams should be a compound selector (and the generateFacetParams added outside the compound selector)