Bug: Designer -> Table Graph does not show record links, when inside record ids

[cguentherTUChemnitz]

Describe the bug

Following the official explenation for usage for timeseries tables: https://surrealdb.com/docs/surrealdb/models/time-series, I am using complex record ids in schemaful tables:

DEFINE TABLE IF NOT EXISTS temperature SCHEMAFULL;
DEFINE FIELD OVERWRITE id ON temperature TYPE [datetime, record<sensor>];

DEFINE FIELD OVERWRITE created_at ON temperature TYPE datetime DEFAULT time::now() READONLY;
DEFINE FIELD OVERWRITE updated_at ON temperature TYPE datetime VALUE time::now() READONLY;

DEFINE FIELD OVERWRITE degree_c ON temperature TYPE float;

DEFINE INDEX OVERWRITE sensor ON TABLE temperature FIELDS id[1];

But the table view does not show the connetion of temperature -> sensor

Steps to reproduce

1. Create a schemafull table containing a record link inside it's id.
2. lookup in surreallist the designer -> Table graph view: now linkage visible between the tables

Expected behaviour

surreallist the designer -> Table graph view should show the linkage between tables, even when the record link is inside a complex record id (especially when ensured by schema)

Surrealist Environment

payed cloud instance of surrealist:

Platform: Web
Navigator: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36
Version: 3.6.9
Flags: feature_flags: false, query_view: true, explorer_view: true, graphql_view: true, designer_view: true, auth_view: true, functions_view: true, parameters_view: true, apidocs_view: true, themes: true, syntax_themes: false, newsfeed: true, database_version_check: true, highlight_tool: false, legacy_serve: false, cloud_enabled: true, cloud_endpoints: production, cloud_access: true, cloud_killswitch: true, changelog: auto, website_base: production, support_tickets_endpoint: production, support_tickets: false, sidebar_customization: false, gtm_debug: false, sidekick_ai: true, v3_migration_tooling: false

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct