-
Notifications
You must be signed in to change notification settings - Fork 3
feat: rename evidence to attachments and update schema #121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
aspiers
merged 1 commit into
hypercerts-org:develop
from
Kzoeps:fix/attachments-schema-update
Jan 29, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| --- | ||
| "@hypercerts-org/sdk-core": minor | ||
| --- | ||
|
|
||
| Rename evidence records to attachments and update schema to match lexicon changes | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| **API Symbol Renames:** | ||
|
|
||
| - `addEvidence()` → `addAttachment()` | ||
| - `CreateHypercertEvidenceParams` → `CreateAttachmentParams` | ||
| - `evidenceUris` → `attachmentUris` in create results | ||
| - `evidenceAdded` → `attachmentAdded` event | ||
| - Evidence type exports replaced with Attachment equivalents | ||
|
|
||
| **Schema Field Changes:** | ||
|
|
||
| **Subject Fields:** | ||
|
|
||
| - `subjectUri` (string) → `subjects` (array of StrongRefs or a single uri or StrongRef) | ||
| - `subject` (StrongRef) → `subjects` (array of StrongRefs or a single uri or StrongRef) | ||
|
|
||
| **Content Fields:** | ||
|
|
||
| - `content` (string | Blob) | Array<(string | Blob)> → `content` (required array of URI/Blob refs) | ||
| - Content is now required and can be an array with multiple items or a single item. SDK will convert to an array | ||
|
|
||
| **Removed Fields:** | ||
|
|
||
| - `relationType` - removed from attachment schema | ||
| - `contributors` - removed from attachment schema | ||
| - `locations` - removed from attachment schema | ||
|
|
||
| **Payload Mapping Examples:** | ||
|
|
||
| ```typescript | ||
| // Old evidence payload | ||
| { | ||
| subjectUri: "at://did:plc:abc/org.hypercerts.claim.activity/xyz", | ||
| content: "https://example.com/report.pdf", | ||
| title: "Report", | ||
| relationType: "supports" | ||
| } | ||
|
|
||
| // New attachment payload | ||
| { | ||
| subjects: "at://did:plc:abc/org.hypercerts.claim.activity/xyz", | ||
| content: "https://example.com/report.pdf", | ||
| title: "Report" | ||
| // relationType removed | ||
| } | ||
|
Kzoeps marked this conversation as resolved.
|
||
| // or arrays: | ||
| { | ||
| subjects: ["at://did:plc:abc/org.hypercerts.claim.activity/xyz", "at://did:plc:abc/org.hypercerts.claim.activity/zyx"] | ||
| content: ["https://reportfile.com/pdf", File] | ||
| } | ||
| ``` | ||
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.