Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move suave-enabled api backends to suave package #56

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

ferranbt
Copy link
Collaborator

@ferranbt ferranbt commented Oct 2, 2023

📝 Summary

This PR introduces two changes:

  • It moves the "SUAVE-enabled node" jsonrpc implementations to their own package outside the upstream logic.
  • It introduces an end-to-end test to ensure that both client and server are compatible.

The goal of this PR is to isolate the custom SUAVE changes and be able to namespace those endpoints differently in a followup PR.

📚 References


  • I have seen and agree to CONTRIBUTING.md

@@ -319,6 +320,12 @@ func makeExtraData(extra []byte) []byte {
func (s *Ethereum) APIs() []rpc.API {
apis := ethapi.GetAPIs(s.APIBackend)

// Append SUAVE-enabled node backend
apis = append(apis, rpc.API{
Namespace: "eth", // TODO
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Change this to have a different namespace. This isolation was not possible before.

@ferranbt ferranbt merged commit 56c777a into main Oct 2, 2023
4 checks passed
@ferranbt ferranbt deleted the decouple-suave-enabled-backend branch October 2, 2023 14:55
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.

2 participants