Paul Rastoin
ca3383cd86
# Introduction The workspace migration runner v2 now computes the next flatObjectMetadataMaps post current ws migration action has been run So the following one have an up to date informations ## Still TODO ~~Remove any contextual information from workspace migration v2 and consume the optimistic cache to retrieve them~~ ## Next steps - Create flat-object-metadata-maps testing toolbox and flat-object/field testing toolbox - Implement strong coverage on every created utils/transpiler and applyWorkspaceMigrationAction method
16 lines
562 B
TypeScript
16 lines
562 B
TypeScript
import {
|
|
appendCommonExceptionCode,
|
|
CustomException,
|
|
} from 'src/utils/custom-exception';
|
|
|
|
export class FlatObjectMetadataMapsException extends CustomException<
|
|
keyof typeof FlatObjectMetadataMapsExceptionCode
|
|
> {}
|
|
|
|
export const FlatObjectMetadataMapsExceptionCode = appendCommonExceptionCode({
|
|
FIELD_METADATA_NOT_FOUND: 'FIELD_METADATA_NOT_FOUND',
|
|
OBJECT_METADATA_NOT_FOUND: 'OBJECT_METADATA_NOT_FOUND',
|
|
FIELD_METADATA_ALREADY_EXISTS: 'FIELD_METADATA_ALREADY_EXISTS',
|
|
OBJECT_METADATA_ALREADY_EXISTS: 'OBJECT_METADATA_ALREADY_EXISTS',
|
|
} as const);
|