Repository navigation
Tags
Tags
Fix - Remove signFileUrl method (twentyhq#19121) `signFileUrl` is the old way to resolve file url. Replaced by `signFileByIdUrl` which needs `FileFolder` and `fileId`. Fix also avatar for person and workspaceMember. To be continued with imageIdentifier refactor. Fix : - https://discord.com/channels/1130383047699738754/1486723854910099576 - https://discord.com/channels/1130383047699738754/1484566445584285870 - https://discord.com/channels/1130383047699738754/1487124612889313420 --------- Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com>
Fix backfill record page layout command (twentyhq#19043) Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com>
fix: use workspace-generated id for core dual-write in message folder… … save (twentyhq#19038) Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com>
fix: gate command-menu-items query behind feature flag (twentyhq#19029) ## Summary - Gate the `FindManyCommandMenuItems` GraphQL query behind the `IS_COMMAND_MENU_ITEM_ENABLED` feature flag on the frontend, preventing an uncaught error when the flag is not enabled for a workspace - Remove `IS_CONNECTED_ACCOUNT_MIGRATED` from the default feature flags list
Combine and clean upgrade commands for record page layouts (twentyhq#… …19004) - Remove the label identifier field for all standard objects as it's a first-class citizen that is displayed specifically in the app; it doesn't make a lot of sense to display it in the Fields widgets - Disable logic that made the label identifier required and in first position - Add all fields for all standard objects in record page layout view fields - Do not include position and ts vector fields in custom objects > [!IMPORTANT] > The command will create Field widgets for all relations. It is consistent to the way the frontend dynamically generates them as of today. We will have to decide which relations we pin as individual Field widgets before the release. (This will likely land in this command or in another one.)
send X-Schema-Version header when metadataVersion is 0 (twentyhq#18924) Fixes twentyhq#13103 Newly created workspaces start with metadataVersion = 0. The truthy check this.currentWorkspace?.metadataVersion && {…} treated 0 as falsy, so the X-Schema-Version header was never sent. Without this header, the backend's schema mismatch detection is bypassed and raw validation errors leak to Sentry. Replaced with isDefined() check. Also replaced bare negation checks with isDefined() in the backend validation hook for consistency.