Strange behavior for offValue from ToggleRefinement / connectToggleRefinement

[AntoineDuComptoirDesPharmacies]

Hi everyone,

The new offValue feature of connectToggleRefinement is very promising because in the past we had to do a custom connector to apply search filters when toggle is unchecked.
However, the UX behavior of offValue seems very strange.

In react-instantsearch-dom the toggle refinement was added to currentRefinements when the user check it. That's it.
It had a certain logic as the user added a filter, and oftenly the currentRefinement is used to display current user filters and allow him to remove them.

In the new widget, when you set a offValue :

• On page arrival, the offValue is not applied to the query, even if the checkbox is off. Nothing in currentRefinements.
• When you toggle, onValue is applied to the query and currentRefinements take new refinement.
• When you untoggle, offValue is applied to the query and currentRefinements take the offvalue refinement.
• If you click on clear from the currentRefinements widget, then neither of both onValue and offValue is applied

What we expected :

• On page arrival, the offValue is applied because toggle is off. Nothing in currentRefinements as it do not result from user interaction (same behavior as Configure node)
• When you toggle, onValue is applied to the query and currentRefinements take new refinement.
• When you untoggle, offValue is applied to the query and currentRefinements remove the onValue refinement
• Clicking the clear of currentRefinements should only untoggle and go back to offValue

Codepen here : https://codesandbox.io/s/focused-leaf-yoj3je?file=/src/App.tsx

What do your think of our UX expectations ?

Yours faithfully,
LCDP