Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(connectors): don't expose duplicates of canRefine #6484

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Dec 19, 2024

In the past, canRefine has been introduced as a consistent way to check if any widget can be refined. There were previous largely overlapping pieces of information exposed which were deprecated. These are now removed.

FX-3195

BREAKING CHANGE: clearRefinements: replace hasRefinements with canRefine
BREAKING CHANGE: hitsPerPage: replace hasNoResults with !canRefine
BREAKING CHANGE: numericMenu: replace hasNoResults with !canRefine
BREAKING CHANGE: ratingMenu: replace hasNoResults with !canRefine
BREAKING CHANGE: sortBy: replace hasNoResults with !canRefine

@Haroenv Haroenv requested review from dhayab and sarahdayan December 19, 2024 16:26
Copy link

codesandbox-ci bot commented Dec 19, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 6c176f8:

Sandbox Source
example-instantsearch-getting-started Configuration
example-react-instantsearch-getting-started Configuration
example-react-instantsearch-next-app-dir-example Configuration
example-react-instantsearch-next-routing-example Configuration
example-vue-instantsearch-getting-started Configuration

@Haroenv Haroenv added this to the instantsearch.js v5 milestone Dec 20, 2024
@Haroenv Haroenv force-pushed the next branch 2 times, most recently from 7ff6737 to b37ba30 Compare December 26, 2024 16:08
@Haroenv Haroenv force-pushed the fix/connectors-canrefine branch from eb71d75 to 84b17ba Compare December 26, 2024 16:18
In the past, `canRefine` has been introduced as a consistent way to check if any widget can be refined. There were previous largely overlapping pieces of information exposed which were deprecated. These are now removed.

[FX-3195]

BREAKING CHANGE: clearRefinements: replace `hasRefinements` with `canRefine`
BREAKING CHANGE: hitsPerPage: replace `hasNoResults` with `!canRefine`
BREAKING CHANGE: numericMenu: replace `hasNoResults` with `!canRefine`
BREAKING CHANGE: ratingMenu: replace `hasNoResults` with `!canRefine`
BREAKING CHANGE: sortBy: replace `hasNoResults` with `!canRefine`
@Haroenv Haroenv force-pushed the fix/connectors-canrefine branch from 84b17ba to 6c176f8 Compare December 26, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant