Custom data
Optional
fetchedThe URI that the metadata was fetched from with placeholders replaced.
Optional
metadataThe metadata fetched by the URI
Optional
toFlag to denote if the metadata is new and should be updated. Used internally.
The URI that the metadata was fetched from. This is the original on-chain URI, so may still have placeholders (i.e. {id} or {address})
Deep copies the object and returns a new instance.
Converts the object to a different NumberType equivalent.
Compares this object's fields to another object's fields for equality. Equality is determined by comparing the JSON representations of the objects.
If normalizeNumberTypes
is true, then all number types will be compared as strings (i.e. "1n" === "1" === 1). Else, they will be compared as their native types (i.e. 1n !== 1 !== "1").
Optional
normalizeNumberTypes: booleanStatic
batchBatch update the metadataArr with the given metadata and badgeIds fetched from the given
Static
getReturns the { metadata, uri, badgeIds, customData } metadata object from the BadgeMetadataDetails
If the badgeId does not exist in the BadgeMetadataDetails
Static
getReturns the metadata from the BadgeMetadataDetails
If the badgeId does not exist in the BadgeMetadataDetails
Static
removeRemoves the metadata from the BadgeMetadataDetails
Note that this function does not mutate the metadataArr, but instead returns a new one.
Static
setFor each badgeId in badgeIds, populates the metadata array with the given key, value JSON property pair.
If you want to update the entire metadata (not just a specific key value pair), use updateBadgeMetadata instead.
This is typically used when customizing or creating a badge.
Static
updateUpdate the metadataArr with the given metadata and badgeIds fetched from the given uri.
Note that this function does not mutate the metadataArr, but instead returns a new one.
The badge IDs that correspond to the metadata