Replies: 1 comment
-
We saw this possibly being confusing, but in the end indeed went with "only facet ordering, not mixing between sortBy & facetOrdering", as both options could be considered confusing. What you can do as a workaround is sort in refinementList({
sortBy: undefined,
transformItems(items) { return items.sort((a, b) => a.isRefined < b.isRefined) }
}) example: https://codesandbox.io/s/kind-http-381ut?file=/src/app.js |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I have a use case where I don't want the default sort to include
isRefined
when using the refinement list connector, so I pass a value of["count:desc", "name:asc"]
tosortBy
, but I still want any facet display ordering to override my sort if set.Related line:
src/connectors/refinement-list/connectRefinementList.ts#L388
I realized that have to leave the default sort to keep
facetOrdering
. It'd be very useful to be able to customize both the default sort and still have the option to keepfacetOrdering
enabled.Beta Was this translation helpful? Give feedback.
All reactions