Skip to content

Conversation

@priscilawebdev
Copy link
Member

Recently, we decided to introduce the prop menuPlacement="auto" as the default behavior for ReactSelect (see).

However, I noticed through the PR that this default was not being applied when the component was a CreatableSelect.

This PR fixes that issue, making menuPlacement="auto" the default for all select components.

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 24, 2025
@priscilawebdev priscilawebdev marked this pull request as ready for review October 24, 2025 08:13
@priscilawebdev priscilawebdev requested a review from a team as a code owner October 24, 2025 08:13
@priscilawebdev priscilawebdev requested review from a team and TkDodo October 24, 2025 08:13
@priscilawebdev priscilawebdev enabled auto-merge (squash) October 24, 2025 08:14
}

return <Component ref={ref as any} {...props} />;
return <Component ref={ref as any} {...props} menuPlacement="auto" />;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Default Prop Overriding User Input

The menuPlacement="auto" prop is placed after {...props}, causing it to override any menuPlacement value passed in props instead of serving as a default. This prevents users from customizing the menu placement.

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bingo. that is what we want!

@priscilawebdev priscilawebdev merged commit c0de8e1 into master Oct 25, 2025
48 checks passed
@priscilawebdev priscilawebdev deleted the priscila/feat/select/make-menu-placement-auto-for-all-selects branch October 25, 2025 02:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants