CP-14721 - Show success toast after DocuSeal document upload - #82
Merged
Conversation
What After uploading or replacing a document in a DocuSeal task form, users now see a short success toast confirming the upload worked Why Upload could finish with no clear feedback, so people weren’t sure whether the document was saved before they continued editing the form How to test 1. Run DocuSeal (foreman start -f Procfile.dev) and open a form at http://localhost:3001 2. On an empty form, upload a PDF/image via the dropzone — expect “Document uploaded successfully” bottom-right, then auto-dismiss ~4s 3. Replace an existing document — expect the same toast once 4. Optional: blank page should not toast; multi-file replace should toast once, not once per file
ryanarakawa
reviewed
Jul 30, 2026
| t.index ["account_id", "event_datetime"], name: "index_email_events_on_account_id_and_event_datetime" | ||
| t.index ["email"], name: "index_email_events_on_email" | ||
| t.index ["email"], name: "index_email_events_on_email_event_types", where: "((event_type)::text = ANY ((ARRAY['bounce'::character varying, 'soft_bounce'::character varying, 'complaint'::character varying, 'soft_complaint'::character varying])::text[]))" | ||
| t.index ["email"], name: "index_email_events_on_email_event_types", where: "((event_type)::text = ANY (ARRAY[('bounce'::character varying)::text, ('soft_bounce'::character varying)::text, ('complaint'::character varying)::text, ('soft_complaint'::character varying)::text]))" |
Collaborator
There was a problem hiding this comment.
Is this just a weird Node/Postgres mismatch or something? I vaguely remember this would happen every now and then at the beginning of the project.
ryanarakawa
approved these changes
Jul 30, 2026
ryanarakawa
left a comment
ryanarakawa
left a comment
Collaborator
There was a problem hiding this comment.
Looks good, that schema diff might be something to discard or look into in the future.
## What Revert the accidental schema.rb formatting change from the upload toast PR ## Why The index SQL rewrite came from a local dump/version difference and is unrelated to the toast work ## How to test Confirm PR no longer includes db/schema.rb; toast behavior unchanged
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
2 participants
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.
CP-14721
What
After uploading or replacing a document in a DocuSeal task form, users now see a short success toast confirming the upload worked
Why
Upload could finish with no clear feedback, so people weren’t sure whether the document was saved before they continued editing the form
How to test
Screenshot