Added definition for bag#975
Conversation
- Added definition for `bag` and described differences between bags and sets
Deploying with
|
| Latest commit: |
6b94d52
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://08e5f988.documentation-7tp.pages.dev |
| Branch Preview URL: | https://kbennett2000-patch-3.documentation-7tp.pages.dev |
dckc
left a comment
dckc
left a comment
There was a problem hiding this comment.
This is different from what I had in mind; when looking for suggestions, I found even more existing problems. I'm not sure how many of them to bite off just now.
| [Purses](#purse) and [payments](#payment) are AssetHolders. These are objects that contain | ||
| digital assets in the quantity specified by an [amount](#amount). | ||
|
|
||
| ## Bag |
There was a problem hiding this comment.
What I had in mind was not defining the general concept of Bag, but making a link between discussion of semi-fungible (e.g. in the glossary entry) and the discussion of AssetKind.COPY_BAG. Looks like the latter is in /reference/ertp-api/ertp-data-types.html#assetkind
Ugh... It looks like "AmountValues are arrays of objects." got copied from the AssetKind.COPY_SET bullet to the AssetKind.COPY_BAG bullet, where it doesn't apply.
There's some good docs in the source code:
Here's hoping for time to talk about how to meld that with the docs site.
2 participants
bagand described differences between bags and sets