fix(cli): update test to match new JSON content format #76
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.
Problem
The
message-actionsmerge changed the CLI's JSON output format for messages. Previously, themessage list --jsoncommand output:{"content": {"Public": {"plaintext": "message text"}}}Now it outputs:
{"content": "message text"}This is because the CLI now uses
effective_text()which returns a plain String (allowing edited message content), rather than serializing the rawRoomMessageBodystructure.The test's
decode_plaintext_messagesfunction expected the old nested format, causing the six-peer-regression test in freenet-core CI to fail with "room1-user1 missing expected messages".Solution
Updated
decode_plaintext_messagesto extract thecontentfield directly as a string, matching the new JSON format.Testing
Impact
Fixes freenet-core CI's six-peer-regression test which is currently failing due to this format mismatch.
[AI-assisted - Claude]