fix: update DDO handling for version compatibility in asset creation

Author: AdriGeorge

src/commands.ts

@@ -81,14 +81,15 @@ export class Commands {
 		const encryptDDO = args[2] === "false" ? false : true;
 		try {
 			const ddoInstance = DDOManager.getDDOClass(asset);
+			const { version, services } = ddoInstance.getDDOFields();
 			const { indexedMetadata } = ddoInstance.getAssetFields();
-			const { services } = ddoInstance.getDDOFields();
+			const isV5 = version >= "5.0.0";
 			// add some more checks
 			const urlAssetId = await createAssetUtil(
-				indexedMetadata.nft.name,
-				indexedMetadata.nft.symbol,
+				isV5 ? indexedMetadata.nft.name : asset.indexedMetadata.nft.name,
+				isV5 ? indexedMetadata.nft.symbol : asset.indexedMetadata.nft.symbol,
 				this.signer,
-				services[0].files,
+				isV5 ? services[0].files : asset.services[0].files,
 				asset,
 				this.oceanNodeUrl,
 				this.config,
@@ -116,13 +117,14 @@ export class Commands {
 		// add some more checks
 		try {
 			const ddoInstance = DDOManager.getDDOClass(algoAsset);
+			const { version, services } = ddoInstance.getDDOFields();
 			const { indexedMetadata } = ddoInstance.getAssetFields();
-			const { services } = ddoInstance.getDDOFields();
+			const isV5 = version >= "5.0.0";
 			const algoDid = await createAssetUtil(
-				indexedMetadata.nft.name,
-				indexedMetadata.nft.symbol,
+				isV5 ? indexedMetadata.nft.name : algoAsset.indexedMetadata.nft.name,
+				isV5 ? indexedMetadata.nft.symbol : algoAsset.indexedMetadata.nft.symbol,
 				this.signer,
-				services[0].files,
+				isV5 ? services[0].files : algoAsset.services[0].files,
 				algoAsset,
 				this.oceanNodeUrl,
 				this.config,