Skip to content

feat: add namespace_separator option for RPC methods#1544

Merged
niklasad1 merged 2 commits intoparitytech:masterfrom
YakupAltay:master
Apr 8, 2025
Merged

feat: add namespace_separator option for RPC methods#1544
niklasad1 merged 2 commits intoparitytech:masterfrom
YakupAltay:master

Conversation

@YakupAltay
Copy link
Contributor

Hi @niklasad1 & @tomaka! 👋

I just opened this issue (#1543) after noticing that jsonrpsee doesn’t currently support namespace separators and instead defaults to using underscores.

To address this, I’ve submitted a PR that introduces a namespace_separator option. The implementation seems to be working, but since I’m not deeply familiar with the codebase, tests, or documentation conventions, I’d really appreciate your input.

Your feedback would be super helpful in making this PR production-ready—we're relying on this feature and would love to get it merged.

Thanks in advance! 🙏

Copy link
Contributor

@niklasad1 niklasad1 left a comment

Choose a reason for hiding this comment

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

Thank you for the PR, I see no problem to support this and the code looks clean.

@YakupAltay
Copy link
Contributor Author

YakupAltay commented Apr 4, 2025

Had a few errors with the tests, @niklasad1. But they are resolved now. Would love to hear your thoughts.

@niklasad1
Copy link
Contributor

Had a few errors with the tests, @niklasad1. But they are resolved now. Would love to hear your thoughts.

All right, looks good to me

@niklasad1 niklasad1 requested a review from Copilot April 7, 2025 07:49
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

tests/tests/proc_macros.rs:323

  • Consider adding test coverage for the scenario where namespace_separator is not provided, ensuring that the default '_' behavior is correctly applied.
assert_eq!(&res, "Called with: 1, test");

@YakupAltay
Copy link
Contributor Author

All right, looks good to me

Thanks! I'm excited to see it get merged.

Copy link
Collaborator

@jsdw jsdw 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!

@niklasad1 niklasad1 merged commit 2219029 into paritytech:master Apr 8, 2025
9 checks passed
@niklasad1 niklasad1 mentioned this pull request Apr 23, 2025
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.

4 participants