You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To handle better the way Select look and feel on Settings, we need to have the ability to choose which kind of select component we want. Currently, on the card forces the use of a styled "Select". But it does not meet the requirements for the Phones Select for instance.
Current behavior
Currently select have to look like this
Expected behavior
We would like to have customisation so that select can look like this :
Technical inputs
We should be able to choose which type of Select we want from the page packages/twenty-front/src/modules/settings/data-model/fields/forms/components/SettingsDataModelFieldSettingsFormCard.tsx. Using {children} sounds like an easy solution to me.
Let's dig into one of the children : SettingsDataModelFieldNumberSettingsFormCard > SettingsDataModelFieldNumberForm . We can see that SettingsOptionCardContentSelect is automatically a '@/ui/input/components/Select' component. It would be great to have the option to choose another type of component.
Scope & Context
To handle better the way Select look and feel on Settings, we need to have the ability to choose which kind of select component we want. Currently, on the card forces the use of a styled "Select". But it does not meet the requirements for the Phones Select for instance.
Current behavior
Currently select have to look like this
Expected behavior
We would like to have customisation so that select can look like this :
Technical inputs
packages/twenty-front/src/modules/settings/data-model/fields/forms/components/SettingsDataModelFieldSettingsFormCard.tsx
. Using{children}
sounds like an easy solution to me.SettingsDataModelFieldNumberSettingsFormCard
>SettingsDataModelFieldNumberForm
. We can see thatSettingsOptionCardContentSelect
is automatically a'@/ui/input/components/Select'
component. It would be great to have the option to choose another type of component.Linked to #8081 and to #8647 and to #8649
The text was updated successfully, but these errors were encountered: