fix: align forest-cli chain message output with lotus #3709
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
As part of #3639
Lotus uses
ChainReadObj
API to print full signed message inlotus chain getmessage [CID]
output, this PR tries to match it inforest-cli chain message -c [CID]
.Note: The output still slightly differs,
forest-cli
printsSignatureType
in string format whilelotus
prints it in Integer format, which has been addressed by #3698Changes introduced in this pull request:
forest-cli chain message -c bafy2bzacedpkf2v5kgm4mvvljer6q3s45yfcdzaiyl3xdoivt5m53iv77v76w
outputlotus chain getmessage bafy2bzacedpkf2v5kgm4mvvljer6q3s45yfcdzaiyl3xdoivt5m53iv77v76w
output:lotus code:
Reference issue to close (if applicable)
Closes
Other information and links
Change checklist