Fix pipeline drag stage persistence - #97
Open
vinay-lgtm-code wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vinay-lgtm-code
force-pushed
the
vinay-lgtm-code/pipeline-stage-renames
branch
from
June 29, 2026 18:12
1030bd3 to
4326b6f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes pipeline drag-and-drop so a moved lead stays in the destination column immediately after confirmation instead of reverting until navigation or browser refresh.
The stage change now goes through a server-side endpoint that resolves the target stage UUID, provisions known missing default stages such as
Decision in Principle done, updates the lead, and records history/activity without writing slugs into the UUID FK.useLeads()now exposes a refetch method so the Pipeline view reconciles local optimistic state with fresh Supabase data after persistence.Validation:
npm run build,npx tsc --noEmit,git diff --check, and local HTTP checks for/pipeline,/leads, and/api/leads/stage-change.