admin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Use main apollo client for workflows (#9675)

Browse Source 
We were using metadata client by legacy. Architecture is not great for
Core engine: workflows are available both in data and metadata client.
It makes more sense to use the data client since workflows are part of
standard objects
This commit is contained in:
Thomas Trompette
2025-01-16 15:21:29 +01:00
committed by GitHub
parent df93b5b311
commit 7ec48b93eb
5 changed files with 9 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
packages/twenty-front/src/modules/workflow/hooks/useComputeStepOutputSchema.ts
View File

@ -1,6 +1,5 @@
import { useApolloMetadataClient } from '@/object-metadata/hooks/useApolloMetadataClient';
import { COMPUTE_STEP_OUTPUT_SCHEMA } from '@/workflow/graphql/mutations/computeStepOutputSchema';
import { useMutation } from '@apollo/client';
import { useApolloClient, useMutation } from '@apollo/client';
import {
ComputeStepOutputSchemaInput,
ComputeStepOutputSchemaMutation,
@ -8,12 +7,12 @@ import {
} from '~/generated/graphql';
export const useComputeStepOutputSchema = () => {
const apolloMetadataClient = useApolloMetadataClient();
const apolloClient = useApolloClient();
const [mutate] = useMutation<
ComputeStepOutputSchemaMutation,
ComputeStepOutputSchemaMutationVariables
>(COMPUTE_STEP_OUTPUT_SCHEMA, {
client: apolloMetadataClient,
client: apolloClient,
});
const computeStepOutputSchema = async (