@docusign/cli 1.2.0-rc → 1.3.0-rc
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -2
- package/dist/index.mjs +421 -227
- package/dist/templates/ai-skills/.claude/skills/ds-package-autopilot/SKILL.md +514 -0
- package/dist/templates/ai-skills/.cursor/rules/docusign.mdc +2 -1
- package/dist/templates/ai-skills/.gemini/instructions.md +2 -1
- package/dist/templates/ai-skills/.github/instructions/docusign.instructions.md +4 -0
- package/dist/templates/ai-skills/aiSkills.spec.ts +57 -0
- package/dist/templates/integration/README.md +40 -0
- package/dist/templates/package/README.md +82 -0
- package/package.json +1 -1
- package/dist/templates/packages/README.md +0 -59
package/README.md
CHANGED
|
@@ -19,8 +19,10 @@ We also provide AI skills that make this easier to use by letting you bring your
|
|
|
19
19
|
Generate `agreement-manager/metadata/metadata.csv` with `ds agm ingest --directory <path> --generate-metadata-template`. The optional `linked_data` column accepts a JSON array matching the Agreement Manager API structure:
|
|
20
20
|
|
|
21
21
|
```csv
|
|
22
|
-
Filename,linked_data
|
|
23
|
-
agreement.pdf,"[{""application_name"":""Salesforce"",""object_name"":""Opportunity"",""record_id"":""006xx000001abc""}]"
|
|
22
|
+
Filename,Filepath,linked_data
|
|
23
|
+
agreement.pdf,legal,"[{""application_name"":""Salesforce"",""object_name"":""Opportunity"",""record_id"":""006xx000001abc""}]"
|
|
24
24
|
```
|
|
25
25
|
|
|
26
|
+
`Filepath` contains the directory relative to the input directory, without the filename. Leave it blank for files directly in that directory. Rows are matched using `Filepath` plus `Filename`, so same-named files in different subdirectories can have distinct metadata. Use `--recursive` to include subdirectories and the same input directory when generating and ingesting. With multiple input directories, paths are relative to the first directory; with `--files` and no input directory, the original file directory paths are preserved, just as in HR mode. Older templates without `Filepath` remain supported only when filenames are unambiguous.
|
|
27
|
+
|
|
26
28
|
Use `ds agm ingest --directory <path> --with-metadata -y` to validate and upload the metadata. A blank cell omits linked data; malformed JSON or invalid linked-data fields stop ingestion before upload.
|