-
Notifications
You must be signed in to change notification settings - Fork 14
feat: implement pgflow vertical slice with anonymous access #290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
View your CI Pipeline Execution ↗ for commit 509ed2a
☁️ Nx Cloud last updated this comment at |
|
|
||
| // Hardcoded local Supabase defaults (Phase 1 - production config in Phase 6) | ||
| const SUPABASE_URL = 'http://127.0.0.1:54321'; | ||
| const SUPABASE_ANON_KEY = 'sb_publishable_ACJWlzQHlZjBrEguHvfOxg_3BJgxAaH'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hardcoded Supabase anon key will need to be replaced with the actual key from your local Supabase instance. To get the correct key, run npx -y supabase@latest status in your terminal and copy the value from the output. This key is environment-specific and the current placeholder won't work with your local setup.
| const SUPABASE_ANON_KEY = 'sb_publishable_ACJWlzQHlZjBrEguHvfOxg_3BJgxAaH'; | |
| const SUPABASE_ANON_KEY = process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY || | |
| (() => { throw new Error('Missing NEXT_PUBLIC_SUPABASE_ANON_KEY. Run `npx -y supabase@latest status` to get your key.') })(); |
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
bb8e938 to
50f3776
Compare
b940998 to
5270efa
Compare
50f3776 to
8c41919
Compare
5270efa to
3cdc7cd
Compare
8c41919 to
70c51db
Compare
70c51db to
eaef789
Compare
3cdc7cd to
5a609dd
Compare
eaef789 to
0fafb70
Compare
5a609dd to
03c77b7
Compare
0fafb70 to
02f3198
Compare
03c77b7 to
1fe1573
Compare
1fe1573 to
9a5ad26
Compare
02f3198 to
6abfbfa
Compare
f1f1476 to
f8e4b97
Compare
…th pgflow integration - Clarify goal to implement a minimal end-to-end flow without authentication - Fix Supabase init command to use npx for latest CLI version - Add schemas to supabase config for pgflow - Include detailed steps for copying core migrations and creating anon permissions - Update vendoring script paths and add Nx target for dependency syncing - Include instructions for building dependencies, creating test flow, and setting up worker - Add steps for testing locally with supabase start and serving functions - Revise UI setup to use Svelte 5 syntax and demonstrate flow start and status updates - Enhance troubleshooting section with relevant checks for vendoring, edge functions, auth, and real-time - Overall, improve clarity for public, unauthenticated demo setup and ensure all steps are aligned for end-to-end testing
396e4b3 to
f2c0d06
Compare
f8e4b97 to
509ed2a
Compare
Merge activity
|
# Implement Minimal End-to-End Flow with Public Anon Key Access This PR implements a minimal end-to-end flow execution from UI button click through Edge Function to real-time status updates. It validates the entire integration stack using only public anonymous key access without requiring authentication. Key changes: - Set up Supabase with pgflow schema and connection pooling - Created a simple test flow with a single step that returns "Hello, World!" - Implemented Edge Function worker to process the flow - Added anon role permissions to allow public access to pgflow functions and tables - Configured real-time updates for runs and step states - Created a minimal UI with a button to start the flow and display status/output - Vendored pgflow packages correctly for Edge Functions - Added proper import maps for Deno The implementation follows a "thinnest possible slice" philosophy, focusing on proving the integration works without authentication. The UI is intentionally minimal but functional, showing real-time status updates and the final output when the flow completes.

Implement Minimal End-to-End Flow with Public Anon Key Access
This PR implements a minimal end-to-end flow execution from UI button click through Edge Function to real-time status updates. It validates the entire integration stack using only public anonymous key access without requiring authentication.
Key changes:
The implementation follows a "thinnest possible slice" philosophy, focusing on proving the integration works without authentication. The UI is intentionally minimal but functional, showing real-time status updates and the final output when the flow completes.