Fix object metadata view creation issue (#9875)

Fixes https://github.com/twentyhq/core-team-issues/issues/26
Fixes https://github.com/twentyhq/twenty/issues/9350
This commit is contained in:
Charles Bochet
2025-01-27 21:25:02 +01:00
committed by GitHub
parent 549c3faf71
commit 4542199e5c
10 changed files with 48 additions and 73 deletions

View File

@ -28,8 +28,7 @@ export const SettingsNewObject = () => {
const navigate = useNavigateSettings();
const { enqueueSnackBar } = useSnackBar();
const { createOneObjectMetadataItem, findManyRecordsCache } =
useCreateOneObjectMetadataItem();
const { createOneObjectMetadataItem } = useCreateOneObjectMetadataItem();
const formConfig = useForm<SettingsDataModelNewObjectFormValues>({
mode: 'onTouched',
@ -53,8 +52,6 @@ export const SettingsNewObject = () => {
? { objectNamePlural: response.createOneObject.namePlural }
: undefined,
);
await findManyRecordsCache();
} catch (error) {
enqueueSnackBar((error as Error).message, {
variant: SnackBarVariant.Error,

View File

@ -137,6 +137,10 @@ export const SettingsObjectNewFieldConfigure = () => {
formValues: SettingsDataModelNewFieldFormValues,
) => {
try {
navigate(SettingsPath.ObjectDetail, {
objectNamePlural,
});
if (
formValues.type === FieldMetadataType.RELATION &&
'relation' in formValues
@ -172,10 +176,6 @@ export const SettingsObjectNewFieldConfigure = () => {
});
}
navigate(SettingsPath.ObjectDetail, {
objectNamePlural,
});
// TODO: fix optimistic update logic
// Forcing a refetch for now but it's not ideal
await apolloClient.refetchQueries({