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

Bug - DualListSelector - Updating availableOptions asynchronously raise TypeError #7538

Closed
Tracked by #8700
guillaumevincent opened this issue Jun 10, 2022 · 2 comments · Fixed by #9901
Closed
Tracked by #8700
Assignees

Comments

@guillaumevincent
Copy link
Contributor

Describe the problem
If you update availableOptions or chosenOptions in an asynchronous function (useEffect or componentDidMount for example). The DualListSelector raise a TypeError: Converting circular structure to JSON.

We only have the issue when the availableOptions or chosenOptions is an array of React Node.

availableOptions={this.state.availableOptions.map(o=><span>{o.name}</span>)} raise the issue

availableOptions={this.state.availableOptions.map(o=>o.name)} don't

How do you reproduce the problem?
https://codesandbox.io/s/vibrant-rhodes-5e5my3?file=/index.js

@nicolethoen nicolethoen added this to the 2022.11 milestone Jun 21, 2022
@mcarrano mcarrano modified the milestones: 2022.11, 2022.13 Aug 19, 2022
@mcarrano mcarrano modified the milestones: 2022.13, 2022.14 Sep 6, 2022
@mcarrano mcarrano added the PF5 label Sep 27, 2022
@mcarrano mcarrano modified the milestones: 2022.14, 2023.02 Sep 27, 2022
@mcarrano mcarrano modified the milestones: 2022.14, 2022.15 Oct 21, 2022
@mcarrano mcarrano removed the PF5 label Oct 21, 2022
@mcarrano mcarrano modified the milestones: 2022.15, 2022.16 Nov 11, 2022
@nicolethoen nicolethoen removed this from the 2022.16 milestone Nov 15, 2022
@stale
Copy link

stale bot commented Jan 14, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale
Copy link

stale bot commented Apr 18, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Apr 18, 2023
@mfrances17 mfrances17 self-assigned this Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants