mukeshs/twenty_crm
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix date field creation with disabled save button (#13416)

Browse Source 
Fixes https://github.com/twentyhq/twenty/issues/13297

See SettingsDataModelFieldDateForm form validation which expects a
settings field to be present with a default display format. This PR adds
the missing initial value.
This commit is contained in:
Weiko
2025-07-24 17:19:40 +02:00
committed by GitHub
parent 88a6913217
commit 3aba04abcd
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
packages/twenty-front/src/modules/settings/data-model/fields/forms/date/hooks/useDateSettingsFormInitialValues.ts
View File

@ -9,10 +9,11 @@ export const useDateSettingsFormInitialValues = ({
}: { }: {
fieldMetadataItem?: Pick<FieldMetadataItem, 'settings'>; fieldMetadataItem?: Pick<FieldMetadataItem, 'settings'>;
}) => { }) => {
const initialDisplayFormat = fieldMetadataItem?.settings const initialDisplayFormat =
?.displayFormat as FieldDateDisplayFormat; (fieldMetadataItem?.settings?.displayFormat as FieldDateDisplayFormat) ??
const initialCustomUnicodeDateFormat = fieldMetadataItem?.settings FieldDateDisplayFormat.USER_SETTINGS;
?.customUnicodeDateFormat as string; const initialCustomUnicodeDateFormat =
(fieldMetadataItem?.settings?.customUnicodeDateFormat as string) ?? '';
const { resetField } = useFormContext<SettingsDataModelFieldDateFormValues>(); const { resetField } = useFormContext<SettingsDataModelFieldDateFormValues>();