Skip to content

fix(filterable-select): refactor updateValues to avoid rerender issue#7920

Draft
robinzigmond wants to merge 1 commit into
masterfrom
refactor-filterable-select-updatevalues
Draft

fix(filterable-select): refactor updateValues to avoid rerender issue#7920
robinzigmond wants to merge 1 commit into
masterfrom
refactor-filterable-select-updatevalues

Conversation

@robinzigmond

Copy link
Copy Markdown
Contributor

refactor updateValues to not use a functional state update, which is unnecessary here. The calling of other state update functions inside this function is likely to be the cause of recursive rerender issues that we are seeing.

fix #7919

Proposed behaviour

Current behaviour

Checklist

  • Commits follow our style guide
  • Related issues linked in commit messages if required
  • Screenshots are included in the PR if useful
  • All themes are supported if required
  • Unit tests added or updated if required
  • Playwright automation tests added or updated if required
  • Storybook added or updated if required
  • Translations added or updated (including creating or amending translation keys table in storybook) if required
  • Typescript d.ts file added or updated if required
  • Related docs have been updated if required

QA

  • Tested in provided StackBlitz sandbox/Storybook
  • Add new Playwright test coverage if required
  • Carbon implementation matches Design System/designs
  • UI Tests GitHub check reviewed if required

Additional context

Testing instructions

refactor updateValues to not use a functional state update, which is unnecessary here. The calling
of other state update functions inside this function is likely to be the cause of recursive rerender
issues that we are seeing.

fix #7919
@robinzigmond robinzigmond self-assigned this Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

FIlterableSelect - unusual state update pattern, possibly leading to infinite rerender issues on React 18

2 participants