Skip to content

docs: show fixed-date defaultValue for DATE signature fields - #72

Merged
amitsharma-turbodocx merged 1 commit into
mainfrom
docs/field-default-value
Aug 21, 2026
Merged

docs: show fixed-date defaultValue for DATE signature fields#72
amitsharma-turbodocx merged 1 commit into
mainfrom
docs/field-default-value

Conversation

@amitsharma-turbodocx

Copy link
Copy Markdown
Contributor

Summary

DATE signature fields accept an optional defaultValue to pin a fixed date (MM/DD/YYYY) instead of auto-filling with the recipient's signing date. This was undiscoverable in the examples, which only showed bare date fields.

Changes

  • Add a fixed-date defaultValue example to the DATE field in each language's turbosign-advanced example (js, py, go, java, php, ruby).
  • Fix a stale comment in go-sdk/README.md that described defaultValue as text-only — it applies to text, identity, and date fields.

Omitting defaultValue keeps the existing behavior (the field auto-fills with the recipient's signing date).

Type of change

Docs only — no library code changed.

DATE signature fields accept an optional defaultValue to pin a fixed date
(MM/DD/YYYY) instead of auto-filling with the recipient's signing date. The
advanced examples showed date fields without it, so add a fixed-date example
to each of the six languages, and correct the go-sdk README comment that
described defaultValue as text-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@amitsharma-turbodocx
amitsharma-turbodocx merged commit 5772a0a into main Aug 21, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant