[fix] Migrated links field should be standard #6387
Conversation
| @@ -225,6 +225,7 @@ export class MigrateLinkFieldsToLinksCommand extends CommandRunner { | |||
| id: tmpNewLinksField.id, | |||
| workspaceId: tmpNewLinksField.workspaceId, | |||
| name: `${fieldName}`, | |||
| isCustom: false, | |||
There was a problem hiding this comment.
when using the service, create endpoint overrides input value for isCustom, but update does not
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Summary
The pull request focuses on fixing the script and adding logs to the sync-metadata process to ensure the migrated links field is standardized.
-
File:
packages/twenty-server/src/database/commands/upgrade-version/0-23/0-23-migrate-link-fields-to-links.command.ts- Added
isCustom: falseto mark migrated fields as standard. - Enhanced logging for better migration visibility.
- Added
-
File:
packages/twenty-server/src/engine/workspace-manager/workspace-sync-metadata/commands/sync-workspace-metadata.command.ts- Added logging statements to improve traceability during workspace synchronization.
Ensure the isCustom property is correctly handled across all related services and thoroughly test the migration script to avoid data inconsistencies.
2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings
Fixing script + ading logs to sync-metadata