refactor: consolidate flow registration in index.ts and remove flows.ts#437
Conversation
|
|
View your CI Pipeline Execution ↗ for commit 4e4bae3
☁️ Nx Cloud last updated this comment at |
jumski
force-pushed
the
11-27-update_docs_for_auto-compilation_flow_and_remove_flows.ts
branch
from
f5358e2 to
df2a149
Compare
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| npx pgflow@0.9.0 install | ||
| ``` | ||
|
|
||
| This creates the ControlPlane edge function at `supabase/functions/control-plane/`. |
There was a problem hiding this comment.
The documentation states the function is created at supabase/functions/control-plane/ but the actual path is supabase/functions/pgflow/ as shown throughout the rest of the PR. This will mislead users about where to find and modify the edge function.
- This creates the ControlPlane edge function at `supabase/functions/control-plane/`.
+ This creates the ControlPlane edge function at `supabase/functions/pgflow/`.| This creates the ControlPlane edge function at `supabase/functions/control-plane/`. | |
| This creates the ControlPlane edge function at `supabase/functions/pgflow/`. |
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
jumski
force-pushed
the
11-27-update_docs_for_auto-compilation_flow_and_remove_flows.ts
branch
from
df2a149 to
4e4bae3
Compare
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-437.pgflow.pages.dev 📝 Details:
_Last updated: _ |
Merge activity
|
…ts (#437) # Update Flow Registration to Use Single File This PR simplifies the pgflow architecture by consolidating flow registration into a single file. Instead of using a separate `flows.ts` file, flows are now registered directly in the `index.ts` file of the pgflow edge function. Key changes: - Removed `flows.ts` and moved flow registration directly into `index.ts` - Updated error messages and documentation to reference `index.ts` instead of `flows.ts` - Added a new documentation page explaining the auto-compilation architecture - Updated the getting started guide to reflect the new registration pattern - Modified tests to match the new file structure This change makes flow registration more straightforward for users and reduces the number of files they need to manage. The documentation now clearly explains how to register flows and how the auto-compilation process works.
1 participant
Update Flow Registration to Use Single File
This PR simplifies the pgflow architecture by consolidating flow registration into a single file. Instead of using a separate
flows.tsfile, flows are now registered directly in theindex.tsfile of the pgflow edge function.Key changes:
flows.tsand moved flow registration directly intoindex.tsindex.tsinstead offlows.tsThis change makes flow registration more straightforward for users and reduces the number of files they need to manage. The documentation now clearly explains how to register flows and how the auto-compilation process works.