-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
FEATURE: Allow an arbitrary JSON string to be send as MetaData using the NFT api #466
Comments
satran004
added a commit
that referenced
this issue
Nov 10, 2024
satran004
added a commit
that referenced
this issue
Nov 19, 2024
…adataList / New methods in MetadataBuilder (#467) * #466 Make json object --> CBOR Map and json array --> CBOR Array methods public and handle null value * #466 fixed tests * #466 Handle BigInteger encoded as ByteString * Add unit tests and improve metadata JSON handling Added several new unit tests for MetadataBuilder and improved the handling of byte strings in the metadata converter. Also included multiple new test JSON files to cover different metadata scenarios. * To fix Sonarcloud warnings
edridudi
pushed a commit
to adabox-aio/cardano-client-lib
that referenced
this issue
Feb 27, 2025
… CBORMetadataList / New methods in MetadataBuilder (bloxbean#467) * bloxbean#466 Make json object --> CBOR Map and json array --> CBOR Array methods public and handle null value * bloxbean#466 fixed tests * bloxbean#466 Handle BigInteger encoded as ByteString * Add unit tests and improve metadata JSON handling Added several new unit tests for MetadataBuilder and improved the handling of byte strings in the metadata converter. Also included multiple new test JSON files to cover different metadata scenarios. * To fix Sonarcloud warnings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to suggest to expand the functionality of the NFT api to allow the input of a well formatted JSON string of arbitrary length. Of course not exceeding the maximum size of the transaction.
The text was updated successfully, but these errors were encountered: