fix: build errors

AElfProject · Jun 24, 2024 · c3dfc87 · c3dfc87
1 parent 1381744
commit c3dfc87
Show file tree

Hide file tree

Showing 8 changed files with 18 additions and 15 deletions.
diff --git a/docs/Architecture/Smart Contract/architecture.md b/docs/Architecture/Smart Contract/architecture.md
@@ -24,7 +24,7 @@ A smart contract consists of methods that interact with state variables. Transac
 
 aelf defines Smart Contracts as micro-services, making them language-independent. For example, the Consensus Protocol is a service defined by a smart contract.
 
-![Smart Contract Architecture](../../_images/sc-as-service.png)
+<!-- ![Smart Contract Architecture](../../_images/sc-as-service.png) -->
 
 ### Chain Interactions
 

diff --git a/...Smart Contract/requirements-and-restrictions/namespace-and-type-restrictions.md b/...Smart Contract/requirements-and-restrictions/namespace-and-type-restrictions.md
@@ -24,10 +24,10 @@ When deploying new contract code, Nodes perform checks against a whitelist. If a
 | Type                          | Member (Field / Method) | Allowed   |
 |-------------------------------|-------------------------|-----------|
 | Array                         | AsReadOnly              | Allowed   |
-| Func<T>                       | ALL                     | Allowed   |
-| Func<T,T>                     | ALL                     | Allowed   |
-| Func<T,T,T>                   | ALL                     | Allowed   |
-| Nullable<T>                   | ALL                     | Allowed   |
+| Func\<T\>                       | ALL                     | Allowed   |
+| Func\<T,T\>                     | ALL                     | Allowed   |
+| Func\<T,T,T\>                   | ALL                     | Allowed   |
+| Nullable\<T\>                   | ALL                     | Allowed   |
 | Environment                   | CurrentManagedThreadId  | Allowed   |
 | BitConverter                  | GetBytes                | Allowed   |
 | NotImplementedException       | ALL                     | Allowed   |

diff --git a/...ntract/requirements-and-restrictions/structure-restrictions-and-requirements.md b/...ntract/requirements-and-restrictions/structure-restrictions-and-requirements.md
@@ -10,7 +10,7 @@
 
 If these rules are not followed, code deployment will fail.
 
-![Contract Class Structure](../../_images/contract-class-structure.png)
+<!-- ![Contract Class Structure](../../_images/contract-class-structure.png) -->
 
 ## Field Usage Limitations
 

diff --git a/docs/Reference/ACS Introduction/ACS10 - Dividend Pool Standard.md b/docs/Reference/ACS Introduction/ACS10 - Dividend Pool Standard.md
@@ -362,11 +362,14 @@ await tokenHolderContractStub.RegisterForProfits.SendAsync(new RegisterForProfit
 ```
 
 - Implement Donate to reduce the account balance by another 10 ELF:
+
+```cs
 await acs10DemoContractStub.Donate.SendAsync(new DonateInput
 {
     Symbol = "ELF",
     Amount = amount
 });
+```
 
 - Test the GetUndistributedDividends and GetDividends:
 ```cs

diff --git a/docs/Reference/ACS Introduction/ACS4 - Consensus Standard.md b/docs/Reference/ACS Introduction/ACS4 - Consensus Standard.md
@@ -166,10 +166,10 @@ ACS4 methods correspond to the IConsensusService interface in the AElf.Kernel.Co
 | ACS4 Method                        | IConsensusService Method          | Methodology                                                                                      | Timing                                                                                                                                                                      |
 |------------------------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | GetConsensusCommand                | Task TriggerConsensusAsync        | When TriggerConsensusAsync is called, it will use the node's configured account to call the GetConsensusCommand method to obtain block information (ConsensusCommand)       | When the node starts; When the BestChainFoundEventData event is thrown; When consensus data validation fails and needs to be triggered again (IsReTrigger field is true).   |
-| GetConsensusExtraData              | Task<byte[]> GetConsensusExtraDataAsync | When a node produces a block, it generates block header info via IBlockExtraDataService, which calls GetConsensusExtraData in the consensus contract                          | When a node produces a new block.                                                                                                                                           |
-| GenerateConsensusTransactions      | Task<List<Transaction>> GenerateConsensusTransactionsAsync | In the process of generating new blocks, a consensus transaction needs to be generated as one of the system transactions                                                    | When a node produces a new block.                                                                                                                                           |
-| ValidateConsensusBeforeExecution   | Task<bool> ValidateConsensusBeforeExecutionAsync | The IBlockValidationProvider interface allows adding a new block validator. The consensus validator, ConsensusValidationProvider, calls ValidateConsensusBeforeExecution     | When a node produces a new block.                                                                                                                                           |
-| ValidateConsensusAfterExecution    | Task<bool> ValidateConsensusAfterExecutionAsync | The implementation of ValidateBlockAfterExecuteAsync in ConsensusValidationProvider calls ValidateConsensusAfterExecution in the consensus contract                           | When a node produces a new block.                                                                                                                                           |
+| GetConsensusExtraData              | Task\<byte[]\> GetConsensusExtraDataAsync | When a node produces a block, it generates block header info via IBlockExtraDataService, which calls GetConsensusExtraData in the consensus contract                          | When a node produces a new block.                                                                                                                                           |
+| GenerateConsensusTransactions      | Task\<List\<Transaction\>\> GenerateConsensusTransactionsAsync | In the process of generating new blocks, a consensus transaction needs to be generated as one of the system transactions                                                    | When a node produces a new block.                                                                                                                                           |
+| ValidateConsensusBeforeExecution   | Task\<bool\> ValidateConsensusBeforeExecutionAsync | The IBlockValidationProvider interface allows adding a new block validator. The consensus validator, ConsensusValidationProvider, calls ValidateConsensusBeforeExecution     | When a node produces a new block.                                                                                                                                           |
+| ValidateConsensusAfterExecution    | Task\<bool\> ValidateConsensusAfterExecutionAsync | The implementation of ValidateBlockAfterExecuteAsync in ConsensusValidationProvider calls ValidateConsensusAfterExecution in the consensus contract                           | When a node produces a new block.                                                                                                                                           |
 
 ### Example
 Refer to the AEDPoS contract implementation.
diff --git a/docs/Reference/ACS Introduction/ACS7 - Cross Chain Standard.md b/docs/Reference/ACS Introduction/ACS7 - Cross Chain Standard.md
@@ -37,7 +37,7 @@ This involves methods for chain creation and indexing:
 #### acs7.ChainIdAndHeightDict
 | Field                    | Description             | Label     |
 |--------------------------|-------------------------|-----------|
-| `id_height_dict` (map<int32, int64>) | Chain IDs and heights | repeated  |
+| `id_height_dict` (map\<int32, int64\>) | Chain IDs and heights | repeated  |
 
 #### acs7.ChainInitializationData
 | Field                                  | Description                        | Label   |

diff --git a/docs/Reference/ACS Introduction/ACS9 - Contract Profit Dividend Standard.md b/docs/Reference/ACS Introduction/ACS9 - Contract Profit Dividend Standard.md
@@ -23,7 +23,7 @@ ACS9 includes several methods given below:
 #### acs9.ProfitsMap
 | Field         | Type                               | Description                              | Label     |
 |---------------|------------------------------------|------------------------------------------|-----------|
-| value         | map<string, int64>                 | Profits accumulated, symbol -> amount.    | repeated  |
+| value         | map\<string, int64\>                 | Profits accumulated, symbol -\> amount.    | repeated  |
 
 #### acs9.TakeContractProfitsInput
 | Field         | Type   | Description                       | Label     |

diff --git a/docs/devtools/contract-sdk/aelf-sdk-csharp.md b/docs/devtools/contract-sdk/aelf-sdk-csharp.md
@@ -159,7 +159,7 @@ The generated hash type id.
 | Name           | Type                                       | Description                              |
 |----------------|--------------------------------------------|------------------------------------------|
 | contractAddress| AElf.Types.Address                         | The contract address for id generation.  |
-| bytes          | System.Collections.Generic.IEnumerable<Byte>| The bytes for id generation.             |
+| bytes          | System.Collections.Generic.IEnumerable\<Byte\>| The bytes for id generation.             |
 
 ## GetContractAddressByName(hash) `method`
 Get the address of a system contract by its name hash. These hashes are in the SmartContractConstants.cs file.
@@ -218,7 +218,7 @@ Logs information for debugging. Visible only when the node is in debug mode.
 ### Parameters
 | Name | Type                       | Description                             |
 |------|----------------------------|-----------------------------------------|
-| func | System.Func<System.String> | The logic for logging purposes.         |
+| func | System.Func\<System.String\> | The logic for logging purposes.         |
 
 ## RecoverPublicKey() `method`
 Recovers the public key of the transaction sender.
@@ -543,7 +543,7 @@ Generates a hash type ID based on the current contract address and the bytes.
 | Name  | Type                                                    | Description                                  |
 |-------|---------------------------------------------------------|----------------------------------------------|
 | this  | AElf.Kernel.SmartContract.ISmartContractBridgeContext   | An instance of ISmartContractBridgeContext.  |
-| bytes | System.Collections.Generic.IEnumerable{System.Byte}     | The bytes for ID generation.                 |
+| bytes | System.Collections.Generic.IEnumerable\{System.Byte\}     | The bytes for ID generation.                 |
 
 ## GenerateId(this, token) `method`
 Generates a hash type ID based on the current contract address and the token.