KamoCRM

Render signer dates in the recipient's resolved timezone

Featurekamo-signer-monorepo
Shipped
3 ஆகஸ்ட், 2026 அன்று 1:28 AM UTC
Author
Kamo
Commit
8793853

SigningSession gains a required `timeZone` (IANA id) that ESigService resolves from the recipient's member zone, then the org's, then UTC. WelcomeScreen now passes it explicitly to the formatter, so the expiry date depends on neither the viewer's device settings nor the provider's UTC default. Making the field required rather than optional caught the one literal session construction site (preview.ts) at compile time. Also: - call setRequestLocale in the locale layout so translations bind to the URL segment rather than relying on the middleware header alone - assert in the Dockerfile that messages/ survived `turbo prune`, and document why .dockerignore must keep .gitignore out of the build context; without that coupling prune drops the translations and the image ships rendering raw keys with nothing failing until a signer opens the document

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing