• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / supabase / 42745066710
87%

Build:
DEFAULT BRANCH: master
Ran 10 Nov 2026 02:50AM UTC
Jobs 1
Files 194
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

10 Nov 2026 02:46AM UTC coverage: 87.157%. Remained the same
42745066710

push

github

web-flow
Joshenlim/fe 4593 cmd k related resources while in table editor (#53079)

## Context

Building on towards resource-aware Cmd K, the changes done up so far
have all been to allow users to search for database resources from
anywhere in the project, with the intention to get you to the resource
quickly without having to go through the navigation hierarchy of the
dashboard.

This PR explores a way to quickly glance related resources for a table
in the Table Editor through Cmd K for that same intention, but listing
out the policies, triggers or functions that run on the table that
you're currently viewing in the Table Editor. E.g here we've got the
`blog_authors` table opened:
<img width="500" alt="image"
src="https://github.com/user-attachments/assets/78c9b85f-cd30-4564-a264-c1a2a596d5c2"
/>

Policies and triggers are fairly straight forward since we can determine
what's related by their target table. Functions are a bit more fuzzy as
we're trying to find what's related by checking the function definition,
if it does anything to the table. For e.g based on the screenshot above,
`blog_handle_new_user` has this definition which was why it was flagged
<img width="500" alt="image"
src="https://github.com/user-attachments/assets/fb8f3be4-05df-4d87-8440-8b75d95546ae"
/>

We're also deliberately decoupling loading of policies + triggers and
functions since searching functions takes slightly longer, so opting to
load results of policies + triggers first, then lazy load functions
subsequently once results are ready

 ## Performance

As usual, ran a benchmarking session with Claude just to make sure that
the added SQL doesn't cause any performance issues, these are aggregates
of 4–5 runs.

**Catalog size (stress catalog)**

| Query | 2,000 tables | 10,000 tables |
|---|---|---|
| Policies and triggers, hub table (many FKs) | 0.1 ms | 0.5–1.3 ms |
| Policies and triggers, ordinary table | ~0 ms | ~0 ms |
| Functions, every body matches | 1.4 ms | 4–8 ms |
| Function... (continued)

2101 of 2476 branches covered (84.85%)

Branch coverage included in aggregate %.

2887 of 3247 relevant lines covered (88.91%)

201.8 hits per line

Subprojects
ID Flag name Job ID Ran Files Coverage
1 studio-tests 42745066710.1 10 Nov 2026 02:50AM UTC 776
38.56
GitHub Action Run
Source Files on build 42745066710
  • Tree
  • List 194
  • Changed 161
  • Source Changed 0
  • Coverage Changed 161
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #42745066710
  • f87de2f0 on github
  • Prev Build on master (#42687769335)
  • Next Build on master (#42746397042)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc