aelf-command - numeric string was forcibly converted into scientific notation

[AbigailDeng]

Expected Behavior:

When initiating a transaction with a purely numeric string using aelf-command, the input should remain as a numeric string without being converted to scientific notation. This behavior should be consistent across different methods of initiating transactions, including both aelf-command and aelf client.

Specifications:

Input: A numeric string (e.g., "12345678901234567890")
Issue: When using aelf-command to initiate a transaction, the numeric string is automatically converted to scientific notation (e.g., "1.2345678901234567e+19").
Expected Result: The numeric string should be passed as-is, without conversion to scientific notation.
Comparison: Initiating the same transaction via aelf client handles the numeric string correctly without conversion.

Tasks

• fix parseJSON