Skip to content

Conversation

@NagyZoltanPeter
Copy link
Contributor

@NagyZoltanPeter NagyZoltanPeter commented Oct 6, 2025

Description

nim-json-serialization missed to escape backslash (escape char) while converting strings to json format.
In status-im/nim-json-serialization#132 it is fixed.

Changes

  • bump nim-json-serialization with the escaping fix.
  • added test case to cover backslash escaping

Issue

closes #3572

@NagyZoltanPeter NagyZoltanPeter self-assigned this Oct 6, 2025
@NagyZoltanPeter NagyZoltanPeter marked this pull request as ready for review October 6, 2025 13:42
Copy link
Collaborator

@Ivansete-status Ivansete-status left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for it! 💯

@github-actions
Copy link

github-actions bot commented Oct 6, 2025

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:3613

Built from 7b4246a

@NagyZoltanPeter
Copy link
Contributor Author

Due #3616 does bumps nim-json-serialization to the same level, this can be closed without merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: nwaku returns invalid message JSON when contentTopic contains backslashes

4 participants