Audited every className token in the repo by compiling them against the shared
tailwind config and diffing generated selectors. The following dead tokens were
replaced with the intended, existing ones:
- text-sbase -> text-base (document invite email button, botched sm->base edit)
- text-primary-forground -> text-foreground (admin license card; the literal
spelling fix would render 10% lightness text on the dark card, the inherited
foreground colour is the intended look)
- tracking-tigh -> tracking-tight (signing waiting page heading)
- font-sm -> text-sm (4 delete-confirmation dialogs)
- dark:text-muted-background -> dark:text-muted (field drag ghost in 4 flows;
restores the dark mode readability fix intended by #1242)
- placeholder:text-foreground-muted -> placeholder:text-muted-foreground
(command palette input)
- text-medium -> font-medium (org create dialog free plan, matches paid plans)
- text-md -> text-base (envelope drop zone hint)
- justify-left -> justify-start (member invite remove button, no visual change)
- removed stray "gradie" fragment and text-dark (no dark colour exists)
No visual change except where the dead class silently disabled intended
styling (email button size, drag ghost dark mode text, dialog confirm text
size).
Add parentId query param support to documents/templates folder index
pages so View All correctly shows subfolders. Fix search not filtering
unpinned folders on documents page and broken mt- Tailwind class on
templates page.
For document signing embeds, the hash-provided name and email should
only
be used when the recipient doesn't already have values set. For template
signing, the hash values are always allowed.
Also makes the email input editable in V1 embeds when the recipient has
no email, matching V2 behavior.
Ref: documenso/embeds#53
## Description
Add envelopes V2 embedded support
---------
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
## Description
Replace the PDF renderer with an custom image renderer.
This allows us to remove the "react-pdf" dependency and allows us to use
a virtual list to improve performance.
API users were inadvertently sending documents without signature fields,
causing confusion for recipients and breaking their signing flows.
- Add getRecipientsWithMissingFields helper in recipients.ts
- Add server-side validation in sendDocument to block distribution
- Fix v1 API to return 400 instead of 500 for validation errors
- Consolidate UI signature field checks to use isSignatureFieldType
- Add E2E tests for both v1 and v2 APIs
Add fullName prop to signature pad components to automatically populate
typed signature
field with signer's name. Updates signature dialog, type component, and
all signing forms
across embed, document, template, and envelope flows to pass through the
user's full
name for better user experience.
This PR is handles the changes required to support envelopes. The new
envelope editor/signing page will be hidden during release.
The core changes here is to migrate the documents and templates model to
a centralized envelopes model.
Even though Documents and Templates are removed, from the user
perspective they will still exist as we remap envelopes to documents and
templates.
Improves the mobile signing UX making actions available via the floating
navbar more obvious.
Also adds an automatic switch to the complete button once all fields
have been signed.
On larger documents we could accidentally start trying to render fields
while not all pages of the PDF have loaded due to us checking for a
single page existing. This would cause an error to be thrown, hard
locking those documents.
This change resolves this by grabbing the highest page number from the
given fields and using it for the visibility check instead.
## Description
Previously we weren't passing the DocumentMeta to our readonly field
component which is used for displaying completed fields by other
recipients.
Due to this dates that were not using the default format were displaying
as invalid date adding confusion to the signing process.
## Related Issue
Reported via support email.
## Changes Made
- Pass the document meta to the readonly field component.
- Support showing completed fields within the embedding UI.
## Testing Performed
- Manual testing