如何在Hyperledger模型文件中用通用键值数组替换可自定义字段？

Got it, let's sort out how to make your Hyperledger asset model flexible enough for runtime custom fields. Replacing those fixed field1/field2 entries with a dynamic key-value structure is totally doable using Hyperledger's modeling language features.

Step 1: Update Your CTO Model with a Map Type #

Hyperledger's CTO modeling language supports Map types, which are perfect for dynamic key-value pairs. Here's how to revise your asset definition:

asset MyAsset identified by id {
  o String id
  --> MyOwner owner
  o Map<String, String> fields optional
}

Key Notes: #

• Map<String, String> defines a dictionary where both keys and values are strings (adjust the types if you need numeric values, dates, etc.—e.g., Map<String, Integer> for number values).
• The optional keyword means the fields map doesn't have to exist when creating the asset (you can initialize it later in your scripts). If you want it to be a required field, just remove optional.

Step 2: Access & Manipulate the Dynamic Fields in Scripts #

Once your model is updated, you can work with the fields map in your transaction processor scripts (or chaincode logic) just like a regular JavaScript object. Here are common operations:

Initialize the Map (if optional) #

First, make sure the map exists before adding fields (to avoid undefined errors):

// When creating/updating the asset
myAsset.fields = myAsset.fields || {}; // Initialize empty map if it doesn't exist

Add/Update Custom Fields #

// Add a new custom field
myAsset.fields["userPreference"] = "darkMode";
// Update an existing field
myAsset.fields["userPreference"] = "lightMode";

Read Custom Fields #

// Get a specific field's value
const theme = myAsset.fields["userPreference"];
console.log(`User theme preference: ${theme}`);

// Check if a field exists
if ("userPreference" in myAsset.fields) {
  // Do something with the value
}

Iterate Over All Custom Fields #

// Loop through all key-value pairs in the map
for (const [key, value] of Object.entries(myAsset.fields)) {
  console.log(`Custom field: ${key} = ${value}`);
}

Bonus: Support Multiple Value Types (If Needed) #

If you need custom fields to support different data types (strings, numbers, booleans, etc.), you can define a concept to wrap the values, then use that in your map:

// Define a reusable concept for flexible field values
concept FieldValue {
  o String stringValue optional
  o Integer intValue optional
  o Boolean boolValue optional
  o Double doubleValue optional
}

// Update the asset to use this concept in the map
asset MyAsset identified by id {
  o String id
  --> MyOwner owner
  o Map<String, FieldValue> fields optional
}

Then in your scripts, you can assign typed values:

myAsset.fields = myAsset.fields || {};
myAsset.fields["age"] = { intValue: 30 };
myAsset.fields["isActive"] = { boolValue: true };

// Read the typed value
const userAge = myAsset.fields["age"].intValue;

内容的提问来源于stack exchange，提问作者auino