d5c974054d
In this PR: ## Improve recompute metadata cache performance. We are aiming for ~100ms Deleting relationMetadata table and FKs pointing on it Fetching indexMetadata and indexFieldMetadata in a separate query as typeorm is suboptimizing ## Remove caching lock As recomputing the metadata cache is lighter, we try to stop preventing multiple concurrent computations. This also simplifies interfaces ## Introduce self recovery mecanisms to recompute cache automatically if corrupted Aka getFreshObjectMetadataMaps ## custom object resolver performance improvement: 1sec to 200ms Double check queries and indexes used while creating a custom object Remove the queries to db to use the cached objectMetadataMap ## reduce objectMetadataMaps to 500kb <img width="222" alt="image" src="https://github.com/user-attachments/assets/2370dc80-49b6-4b63-8d5e-30c5ebdaa062" /> We used to stored 3 fieldMetadataMaps (byId, byName, byJoinColumnName). While this is great for devXP, this is not great for performances. Using the same mecanisme as for objectMetadataMap: we only keep byIdMap and introduce two otherMaps to idByName, idByJoinColumnName to make the bridge ## Add dataloader on IndexMetadata (aka indexMetadataList in the API) ## Improve field resolver performances too ## Deprecate ClientConfig
24 lines
571 B
TypeScript
24 lines
571 B
TypeScript
import { ClientConfig } from '@/client-config/types/ClientConfig';
|
|
import { createState } from 'twenty-ui/utilities';
|
|
|
|
type ClientConfigApiStatus = {
|
|
isLoadedOnce: boolean;
|
|
isLoading: boolean;
|
|
isErrored: boolean;
|
|
isSaved: boolean;
|
|
error?: Error;
|
|
data?: { clientConfig: ClientConfig };
|
|
};
|
|
|
|
export const clientConfigApiStatusState = createState<ClientConfigApiStatus>({
|
|
key: 'clientConfigApiStatus',
|
|
defaultValue: {
|
|
isLoadedOnce: false,
|
|
isLoading: false,
|
|
isErrored: false,
|
|
isSaved: false,
|
|
error: undefined,
|
|
data: undefined,
|
|
},
|
|
});
|