clapointe-carbonleo gets shared projects to actually show up

A broken visibility filter meant projects shared with a colleague weren't reliably appearing for them - this fixes that, with a catch.

workflowmulti-tenant

When you share a project with someone, the system has to figure out which shared projects to show each person when they log in. clapointe-carbonleo found that the filter doing that job - running inside Supabase, the hosted database behind the fork - was behaving unpredictably and quietly dropping results. The fix sidesteps the database entirely: pull the candidate projects, then sort out who can see what in the application layer instead.

It works, and shared projects now surface correctly. The honest tradeoff, which the commit notes itself, is that it doesn't scale cleanly - every time someone opens their project list, the system now pulls every project they don't own before narrowing down. Fine for a small team, a drag once the data grows. It's a working stopgap, not the final answer.

So what Anyone running a small legal team on this fork gets working project sharing today, but should watch this spot as their matter count climbs.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from clapointe-carbonleo/mike-legal, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`9e02ae0e`	Fix /projects endpoint: filter shared_with client-side	clapointe-carbonleo	2026-05-06	↗ GitHub
The .contains() method doesn't work for JSONB arrays in Supabase JS client. Changed to fetch all non-owned projects and filter by shared_with email client-side. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

SHA

Subject

Author

Date

9e02ae0e

Fix /projects endpoint: filter shared_with client-side

clapointe-carbonleo

2026-05-06

↗ GitHub

The .contains() method doesn't work for JSONB arrays in Supabase JS client.
Changed to fetch all non-owned projects and filter by shared_with email client-side.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-13.md from inside the repo you want the changes in.