Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(site): add preset combobox to dynamic parameters page#19100

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

ssncferreira
Copy link
Contributor

@ssncferreirassncferreira commentedJul 30, 2025
edited
Loading

Description

This PR updates theCreateWorkspacePageViewExperimental page to use theCombobox React component for preset selection. This aligns it with the implementation used in the standardCreateWorkspacePageView, ensuring consistency in UI behavior and component usage across both pages.

Screenshot 2025-07-30 at 13 58 23

Related toCreateWorkspacePageView changes:#19063

@ssncferreirassncferreira marked this pull request as ready for reviewJuly 30, 2025 12:59
@ssncferreirassncferreira merged commit96e32d6 intomainJul 30, 2025
33 checks passed
@ssncferreirassncferreira deleted the ssncferreira/chore-site-dynamic-parameters-preset-icon-description branchJuly 30, 2025 17:03
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJul 30, 2025
Comment on lines +586 to +590
// "undefined" string is equivalent to using None option
// Combobox requires a value in order to correctly highlight the None option
presetOptions[index].value==="undefined"
?undefined
:presetOptions[index].value,
Copy link
Member

Choose a reason for hiding this comment

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

sorry to keep bringing up merged pull requests, but couldn'tvalue just be""? then it wouldn't need this special handling, asundefined gets deserialized the same as"" by the backend

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

@aslilac Ideally, yes, it should be an empty string. However, this appears to be an issue with theCombobox component: when no value is provided, the "None" option doesn't get highlighted on hover like the other options do. This was a workaround to ensure consistent hover behavior, including for the "None" option.

@jaaydenh helped me investigate this and came up with the workaround, so he may have more context.

I've included a recording below showing the difference:

  • When value is "": "None" is not highlighted on hover
Screen.Recording.2025-08-04.at.16.09.20.mov
  • When value is set: "None" is highlighted on hover
Screen.Recording.2025-08-04.at.16.10.17.mov

Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@aslilacaslilacaslilac left review comments

@jaaydenhjaaydenhjaaydenh approved these changes

Assignees

@ssncferreirassncferreira

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@ssncferreira@aslilac@jaaydenh

[8]ページ先頭

©2009-2025 Movatter.jp