fix(atomic): reset input range on facet clear

[y-lakhdar]

https://coveord.atlassian.net/browse/KIT-3240

[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	202.8	202.8	0
commerce	285.9	285.9	0
search	367.4	367.4	0
insight	347.7	347.7	0
product-listing	262.2	262.2	0
product-recommendation	171.9	171.9	0
recommendation	215.8	215.8	0
ssr	360.2	360.2	0

SSR Progress

Use case	SSR (#)	CSR (#)	Progress (%)
search	39	44	89
recommendation	0	4	0
product-recommendation	0	10	0
product-listing	0	13	0
case-assist	0	6	0
insight	0	27	0
commerce	0	7	0

Detailed logs

search : buildInteractiveResult
search : buildInteractiveInstantResult
search : buildInteractiveRecentResult
search : buildInteractiveCitation
search : buildGeneratedAnswer
recommendation : missing SSR support
product-recommendation : missing SSR support
product-listing : missing SSR support
case-assist : missing SSR support
insight : missing SSR support
commerce : missing SSR support

[olamothe]

Humm so we don't tie the range input to any state at all in Headless for commerce ? Why is that 🤔

That's a bit strange, and why we end up with having to handle a stateful property like this in Atomic.

[y-lakhdar]

Humm so we don't tie the range input to any state at all in Headless for commerce ? Why is that 🤔

That's a bit strange, and why we end up with having to handle a stateful property like this in Atomic.

There is already a story about this:
https://coveord.atlassian.net/browse/KIT-3293.

I needed some input on how to handle components that involve multiple controllers.

[y-lakhdar]

to b fixed in a different PR
See #4090