[WIP] auto layout table group

[junkisai]

Issue

• resolve:

Why is this change needed?

What would you like reviewers to focus on?

Testing Verification

What was done

pr_agent:summary

Detailed Changes

pr_agent:walkthrough

Additional Notes

[changeset-bot]

⚠️ No Changeset found

Latest commit: c622c3b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
liam-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2025 11:37am
liam-erd-sample	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2025 11:37am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
liam-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 11, 2025 11:37am

[supabase]

Updates to Preview Branch (feat/auto-layout-table-group) ↗︎

Deployments	Status	Updated
Database	✅	Fri, 11 Apr 2025 11:34:09 UTC
Services	✅	Fri, 11 Apr 2025 11:34:09 UTC
APIs	✅	Fri, 11 Apr 2025 11:34:09 UTC

Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.

Tasks	Status	Updated
Configurations	✅	Fri, 11 Apr 2025 11:34:20 UTC
Migrations	✅	Fri, 11 Apr 2025 11:34:22 UTC
Seeding	✅	Fri, 11 Apr 2025 11:34:22 UTC
Edge Functions	✅	Fri, 11 Apr 2025 11:34:22 UTC

---

View logs for this Workflow Run ↗︎.
Learn more about Supabase for Git ↗︎.

[qodo-merge-pro-for-open-source]

CI Feedback 🧐

(Feedback updated until commit c622c3b)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: e2e-tests (Mobile Safari)

Failed stage: [❌]

Failure summary: The action failed because the operation was canceled (line 1535: "##[error]The operation was canceled."). The Playwright tests were running (17 tests using 1 worker) but were interrupted before completion. This could be due to: A timeout in the GitHub Actions workflow Manual cancellation of the workflow An infrastructure issue on the GitHub Actions runner The log shows the tests were starting to run for the "Mobile Safari" project when the cancellation occurred.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 184: CI: true 185: URL: https://liam-utni8bbgk-route-06-core.vercel.app 186: ENVIRONMENT: Preview – liam-app 187: PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin 188: ##[endgroup] 189: Node version file is not JSON file 190: Resolved ./.node-version as 22.14.0 191: Found in cache @ /opt/hostedtoolcache/node/22.14.0/x64 192: ##[group]Environment details 193: node: v22.14.0 194: npm: 10.9.2 195: yarn: 1.22.22 196: ##[endgroup] 197: [command]/home/runner/setup-pnpm/node_modules/.bin/pnpm store path --silent 198: /home/runner/setup-pnpm/node_modules/.bin/store/v3 199: ##[warning]Failed to restore: Failed to GetCacheEntryDownloadURL: Received non-retryable error: Failed request: (403) Forbidden: unable to access resource in current scope 200: pnpm cache is not found ... 211: Lockfile is up to date, resolution step is skipped 212: Progress: resolved 1, reused 0, downloaded 0, added 0 213: Packages: +1552 214: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 215: Progress: resolved 1552, reused 0, downloaded 171, added 165 216: Progress: resolved 1552, reused 0, downloaded 279, added 266 217: Progress: resolved 1552, reused 0, downloaded 425, added 417 218: Progress: resolved 1552, reused 0, downloaded 531, added 519 219: Progress: resolved 1552, reused 0, downloaded 532, added 519 220: Progress: resolved 1552, reused 0, downloaded 660, added 652 221: Progress: resolved 1552, reused 0, downloaded 856, added 861 222: Progress: resolved 1552, reused 0, downloaded 1041, added 1047 223: Progress: resolved 1552, reused 0, downloaded 1311, added 1324 224: Progress: resolved 1552, reused 0, downloaded 1520, added 1536 225: Progress: resolved 1552, reused 0, downloaded 1531, added 1552, done 226: WARN  Failed to create bin at /home/runner/work/liam/liam/node_modules/.pnpm/node_modules/.bin/supabase. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/node_modules/.pnpm/node_modules/supabase/bin/supabase' 227: .../node_modules/core-js-pure postinstall$ node -e "try{require('./postinstall')}catch(e){}" 228: .../node_modules/@prisma/engines postinstall$ node scripts/postinstall.js 229: .../esbuild@0.25.2/node_modules/esbuild postinstall$ node install.js 230: .../sharp@0.34.1/node_modules/sharp install$ node install/check 231: .../node_modules/@biomejs/biome postinstall$ node scripts/postinstall.js 232: .../node_modules/core-js-pure postinstall: Done 233: .../esbuild@0.25.2/node_modules/esbuild postinstall: Done 234: .../node_modules/@biomejs/biome postinstall: Done 235: .../node_modules/protobufjs postinstall$ node scripts/postinstall 236: .../sharp@0.34.1/node_modules/sharp install: Done 237: .../node_modules/@sentry/cli postinstall$ node ./scripts/install.js 238: .../node_modules/protobufjs postinstall: Done 239: .../node_modules/@prisma/engines postinstall$ node scripts/postinstall.js 240: WARN  Failed to create bin at /home/runner/work/liam/liam/node_modules/.pnpm/supabase@2.20.12/node_modules/supabase/node_modules/.bin/supabase. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/node_modules/.pnpm/supabase@2.20.12/node_modules/supabase/bin/supabase' 241: .../node_modules/supabase postinstall$ node scripts/postinstall.js ... 255: .../node_modules/supabase postinstall: Installed Supabase CLI successfully 256: .../node_modules/supabase postinstall: Done 257: .../node_modules/style-dictionary postinstall$ patch-package 258: .../node_modules/prisma preinstall$ node scripts/preinstall-entry.js 259: .../node_modules/prisma preinstall: Done 260: .../node_modules/style-dictionary postinstall: patch-package 8.0.0 261: .../node_modules/style-dictionary postinstall: Applying patches... 262: .../node_modules/style-dictionary postinstall: No patch files found 263: .../node_modules/style-dictionary postinstall: Done 264: .../node_modules/@prisma/client postinstall$ node scripts/postinstall.js 265: .../node_modules/@prisma/client postinstall: prisma:warn We could not find your Prisma schema in the default locations (see: https://pris.ly/d/prisma-schema-location). 266: .../node_modules/@prisma/client postinstall: If you have a Prisma schema file in a custom path, you will need to run 267: .../node_modules/@prisma/client postinstall: `prisma generate --schema=./path/to/your/schema.prisma` to generate Prisma Client. 268: .../node_modules/@prisma/client postinstall: If you do not have a Prisma schema file yet, you can ignore this message. 269: .../node_modules/@prisma/client postinstall: Done 270: WARN  Failed to create bin at /home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/.bin/liam. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/frontend/packages/cli/dist-cli/bin/cli.js' 271: devDependencies: 272: + @changesets/cli 2.28.1 273: + @changesets/get-github-info 0.6.0 274: + @changesets/types 6.1.0 275: + @turbo/gen 2.5.0 276: + concurrently 9.1.2 277: + syncpack 13.0.3 278: + turbo 2.5.0 279: + vercel 41.5.0 280: frontend/apps/docs postinstall$ fumadocs-mdx 281: frontend/apps/docs postinstall: [MDX] types generated 282: frontend/apps/docs postinstall: Done 283: frontend/apps/app postinstall$ cp ../../packages/db-structure/node_modules/@ruby/prism/src/prism.wasm prism.wasm 284: frontend/apps/app postinstall: Done 285: WARN  Failed to create bin at /home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/.bin/liam. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/@liam-hq/cli/dist-cli/bin/cli.js' 286: Done in 15.3s using pnpm v9.15.9 ... 288: with: 289: path: ~/.cache/ms-playwright 290: key: playwright-Linux-61f1746fb6a759ff7d17d8191b67c28c05c4dd52ddc4f3c7fd07519e5d2a3e6f 291: restore-keys: playwright-Linux- 292: 293: enableCrossOsArchive: false 294: fail-on-cache-miss: false 295: lookup-only: false 296: save-always: false 297: env: 298: CI: true 299: URL: https://liam-utni8bbgk-route-06-core.vercel.app 300: ENVIRONMENT: Preview – liam-app 301: PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin 302: ##[endgroup] 303: [warning]Event Validation Error: The event type deployment_status is not supported because it's not tied to a branch or tag ref. 304: ##[group]Run pnpm exec playwright install --with-deps ... 1520: |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 70% of 2.3 MiB 1521: |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 80% of 2.3 MiB 1522: |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 90% of 2.3 MiB 1523: |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| 100% of 2.3 MiB 1524: FFMPEG playwright build v1011 downloaded to /home/runner/.cache/ms-playwright/ffmpeg-1011 1525: ##[group]Run pnpm exec playwright test --project="Mobile Safari" 1526: �[36;1mpnpm exec playwright test --project="Mobile Safari"�[0m 1527: shell: /usr/bin/bash -e {0} 1528: env: 1529: CI: true 1530: URL: https://liam-utni8bbgk-route-06-core.vercel.app 1531: ENVIRONMENT: Preview – liam-app 1532: PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin 1533: ##[endgroup] 1534: Running 17 tests using 1 worker 1535: ##[error]The operation was canceled. 1536: Post job cleanup.