9ed6edc005
- In this PR the default value of IS_CONFIG_VARIABLES_IN_DB_ENABLED has
been changed to true,
- This is my first time writing integration tests, so I’d appreciate a
thorough review. :)
I’ve tried to follow the existing test patterns closely, but there might
be some small mistakes I may have missed.
Also let me know if I have missed any important test cases that should
be tested
UPDATE -
### Config Value Converter Refactoring
- Created a centralized type transformers registry with bidirectional
validation
- Refactored ConfigValueConverterService to support validation in both
directions:
- Maintained existing DB-to-app conversion behavior
- Added validation for app-to-DB conversion
- Added integration tests to verify validation works in both directions
---------
Co-authored-by: Félix Malfait <felix@twenty.com>
25 lines
570 B
TypeScript
25 lines
570 B
TypeScript
import { gql } from 'apollo-server-core';
|
|
import { ConfigVariableValue } from 'twenty-shared/src/types/ConfigVariableValue';
|
|
|
|
export type UpdateConfigVariableFactoryInput = {
|
|
key: string;
|
|
value: ConfigVariableValue;
|
|
};
|
|
|
|
export const updateConfigVariableQueryFactory = ({
|
|
key,
|
|
value,
|
|
}: UpdateConfigVariableFactoryInput) => {
|
|
return {
|
|
query: gql`
|
|
mutation UpdateDatabaseConfigVariable($key: String!, $value: JSON!) {
|
|
updateDatabaseConfigVariable(key: $key, value: $value)
|
|
}
|
|
`,
|
|
variables: {
|
|
key,
|
|
value,
|
|
},
|
|
};
|
|
};
|