Paul RastoinandGitHub
59d90bedaa
# Introduction Migrating and improving performances of field enum integrations tests success and failing tests cases to be using the new v2 api ## Discovered issue When deleting an object in v1 it will leave related enums until the object is re-created Something not done anymore within the create in v2 but in the delete operation We should implem an upgrade command to remove such relicas ## Bugs - Update/create default value multi select runner wrong sql query -> FIX - Update default value multi select regression, we should allow option without an id to be inserted -> FIX - default value compare dynamic json stringify convertion or not in compare tools for object and fields
29 lines
611 B
TypeScript
29 lines
611 B
TypeScript
import gql from 'graphql-tag';
|
|
|
|
import { type FeatureFlagKey } from 'src/engine/core-modules/feature-flag/enums/feature-flag-key.enum';
|
|
|
|
export const updateFeatureFlagFactory = (
|
|
workspaceId: string,
|
|
featureFlag: FeatureFlagKey,
|
|
value: boolean,
|
|
) => ({
|
|
query: gql`
|
|
mutation UpdateWorkspaceFeatureFlag(
|
|
$workspaceId: UUID!
|
|
$featureFlag: String!
|
|
$value: Boolean!
|
|
) {
|
|
updateWorkspaceFeatureFlag(
|
|
workspaceId: $workspaceId
|
|
featureFlag: $featureFlag
|
|
value: $value
|
|
)
|
|
}
|
|
`,
|
|
variables: {
|
|
workspaceId,
|
|
featureFlag,
|
|
value,
|
|
},
|
|
});
|