feat: allow backend to rename field of custom object (#4097)
* feat: allow backend to rename field of custom object * feat: allow custom field label edition in Settings Closes #4080 * fix: avoid renaming standard fields --------- Co-authored-by: Thaïs Guigon <guigon.thais@gmail.com>
This commit is contained in:
@ -228,9 +228,23 @@ export class FieldMetadataService extends TypeOrmQueryService<FieldMetadataEntit
|
||||
)
|
||||
: fieldMetadataInput;
|
||||
|
||||
const updatedFieldMetadata = await super.updateOne(id, updatableFieldInput);
|
||||
const updatedFieldMetadata = await super.updateOne(id, {
|
||||
...updatableFieldInput,
|
||||
// If the name is updated, the targetColumnMap should be updated as well
|
||||
targetColumnMap: updatableFieldInput.name
|
||||
? generateTargetColumnMap(
|
||||
existingFieldMetadata.type,
|
||||
existingFieldMetadata.isCustom,
|
||||
updatableFieldInput.name,
|
||||
)
|
||||
: existingFieldMetadata.targetColumnMap,
|
||||
});
|
||||
|
||||
if (updatableFieldInput.options || updatableFieldInput.defaultValue) {
|
||||
if (
|
||||
fieldMetadataInput.name ||
|
||||
updatableFieldInput.options ||
|
||||
updatableFieldInput.defaultValue
|
||||
) {
|
||||
await this.workspaceMigrationService.createCustomMigration(
|
||||
generateMigrationName(`update-${updatedFieldMetadata.name}`),
|
||||
existingFieldMetadata.workspaceId,
|
||||
|
||||
Reference in New Issue
Block a user