You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
allow Clarity values to also use number/string/bigint
refactor to use asset-info string everywhere possible, refactor to contract-address-id strings (.) (::)
rename NftString to Asset, since it's the same for FT contracts, update the builders as well
prefer string addresses everywhere (maybe doesn't need to be message type)
make all methods use new network obj, instead of chain-id etc.
consolidate capitalization (camel case vs STX/ID)
remove structured signature from message types (and other non-needed wrapper types)
non-breaking (extra credit)
add pox tuple address helper to the Cl. namespace
add missing tx creation checks (e.g. contract name too long)
add detectable (control flowable) errors everywhere
e.g. FetchError for anything that failed during fetch
errors should still just be a string (and maybe a .originalError)
clean imports everywhere
get rid of comments using [[]] syntax
clean up manual re-exports and always export where defined
The text was updated successfully, but these errors were encountered:
more steps to come 😉
NftString
to Asset, since it's the same for FT contracts, update the builders as wellnon-breaking (extra credit)
e.g. FetchError for anything that failed during fetch
errors should still just be a string (and maybe a .originalError)
The text was updated successfully, but these errors were encountered: