-
Notifications
You must be signed in to change notification settings - Fork 13
fix: remove temp migrations and prepare stack to be merged #230
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
fix: remove temp migrations and prepare stack to be merged #230
Conversation
|
Name | Type |
---|---|
@pgflow/dsl | Minor |
@pgflow/core | Minor |
pgflow | Minor |
@pgflow/client | Minor |
@pgflow/edge-worker | Minor |
@pgflow/example-flows | Minor |
@pgflow/website | Minor |
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
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
pkgs/core/supabase/migrations/20251006063001_pgflow_add_map_step_type.sql
Show resolved
Hide resolved
View your CI Pipeline Execution ↗ for commit 8dc0d99
☁️ Nx Cloud last updated this comment at |
672447d
to
d9bdc7c
Compare
90350c4
to
a2f5600
Compare
d9bdc7c
to
8084414
Compare
… improve failure handling - Renamed existing changesets for clarity - Implemented map step type infrastructure in SQL core - Added .map() method to Flow DSL with compile-time validation and type safety - Enhanced failure handling to archive all pending messages on run failure - Fixed type contract violations to fail immediately without retries - Updated documentation and created detailed changeset - Removed obsolete plan files and consolidated migration strategy - Improved robustness and observability for map steps and failure scenarios
8084414
to
8dc0d99
Compare
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-230.pgflow.pages.dev 📝 Details:
_Last updated: _ |
🔍 Preview Deployment: Playground❌ Deployment failed! Please check the workflow logs for details. |
Merge activity
|
# Remove planning documents now that map infrastructure is complete This PR removes all planning documents that were used during the map infrastructure development. The map feature is now complete and fully integrated into the codebase, making these planning documents obsolete. Specifically: - Removed [PLAN.md](http://PLAN.md) which tracked the map infrastructure implementation progress - Removed PLAN_partial_completion.md which outlined failure handling strategies - Removed PLAN_step_output.md which detailed performance optimization plans - Removed PLAN_race_condition_testing.md which described testing approaches - Consolidated all temporary migrations into a single clean migration These documents served as implementation guides during development but are no longer needed now that the features have been fully implemented. The code itself now serves as the source of truth for how map steps, failure handling, and output aggregation work.
Remove planning documents now that map infrastructure is complete
This PR removes all planning documents that were used during the map infrastructure development. The map feature is now complete and fully integrated into the codebase, making these planning documents obsolete.
Specifically:
These documents served as implementation guides during development but are no longer needed now that the features have been fully implemented. The code itself now serves as the source of truth for how map steps, failure handling, and output aggregation work.