[REQUIRES_CACHE_FLUSH][GQL_VIEW_GROUP_API_BREAKING_CHANGE] ViewGroup in v2 (#15052)
# Introduction Adding view-group to core engine v2 Following https://github.com/twentyhq/twenty/pull/15010 ( same pattern ) ## What's done - Created flat-view-group - flat view group runner - flat view group builder - create view group service v2 and input transpilers - refactor the existing view group resolver to fix standard ( BREAKING_CHANGE on graphql api update especially ) REST stays the same - refactored the front to consume the mutations autogenerated close https://github.com/twentyhq/core-team-issues/issues/1665
This commit is contained in:
+12
@@ -0,0 +1,12 @@
|
||||
import { ALL_METADATA_NAME } from 'src/engine/metadata-modules/flat-entity/constant/all-metadata-name.constant';
|
||||
import { type OrchestratorFailureReport } from 'src/engine/workspace-manager/workspace-migration-v2/types/workspace-migration-orchestrator.type';
|
||||
|
||||
export const EMPTY_ORCHESTRATOR_FAILURE_REPORT = (
|
||||
Object.keys(ALL_METADATA_NAME) as (keyof typeof ALL_METADATA_NAME)[]
|
||||
).reduce(
|
||||
(orchestratorReport, metadataName) => ({
|
||||
...orchestratorReport,
|
||||
[metadataName]: [],
|
||||
}),
|
||||
{} as OrchestratorFailureReport,
|
||||
);
|
||||
Reference in New Issue
Block a user