Debugging issue with *and* operator on useRefinementList hook

[matt-quests-for-tacos]

This just doesn't appear to be working for me, and want to make sure I am not missing something.

Here is some sample code:

const ConnectedFilterWithAndOperator = (
  props: ConnectedFilterWithOperatorProps
) => {
  const { refine, items } = useRefinementList({
    attribute: props.attribute,
    operator: 'and',
    limit: props.limit,
  });

  const { items: currentRefinement } = useCurrentRefinements({
    includedAttributes: [props.attribute],
  });

  return (
    <Filter
      {...props}
      items={items}
      currentRefinement={currentRefinement}
      refine={refine}
      operator={'and'}
    />
  );
};

The currentRefinement -> refinementsList that I get back from the useCurrentRefinements hook has the disjunctive type, and the query that gets built just ignores the AND syntax / request altogether. The or operator works great out of the box, but when I toggle the operator and re render this filter to use the and operator I just cannot get it to work.

Should this current refinement list have the conjunctive type, and is that why the and syntax is just being ignored?

[Haroenv]

Why are you using the currentRefinement from useCurrentRefinements instead of just the isRefined key of items[i]?

[matt-quests-for-tacos]

Good point, I can refactor this to use isRefined on items. However, that doesn't provide any context as to why the and operator on the useRefinementsList hook is just not doing anything.

[Haroenv]

you'd need to give a full reproduction to explain what exactly is going on. I guess it may reset to or at some point and then lose the refinement?

[matt-quests-for-tacos]

Currently there is no good way to toggle the operator on the refinement list. I have noticed that whichever operator is set first when this useRefinementList renders, is what is used, even if I change the operator and re render the component.

Our filters usually default to using the or operator, and hard coding the operator to and resulted in the query formatting the filter values correctly and returning the correct results.

[Haroenv]

Yes, there's few use cases for changing the operator, I suggest you ensure you always use the same operator for the same widget.