The badge IDs corresponding to the URI.
Arbitrary custom data that can be stored on-chain
The URI where to fetch the badge metadata from.
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").
OptionalnormalizeNumberTypes: booleanStaticfromOptionaloptions: Partial<JsonReadOptions>StaticfromOptionaloptions: Partial<JsonReadOptions>StaticfromStaticgetGet first matches for the badge metadata (i.e. if there are duplicated badge IDs, we take the first match in a linear search).
BadgeMetadata is used to represent the metadata for a range of badge IDs. The metadata can be hosted via a URI (via uri) or stored on-chain (via customData).
We take first-match only for the badge IDs. If a badge ID is in multiple BadgeMetadata, we take the first match in a linear search.