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

Add peers v2 without meta #384

Closed
wants to merge 2 commits into from
Closed

Add peers v2 without meta #384

wants to merge 2 commits into from

Conversation

dapplion
Copy link
Member

@dapplion dapplion commented Dec 8, 2023

Any consumer can derive the number of items by just doing len(data). Creating a new route as a property is deleted from the response object

Closes #366

Copy link
Contributor

@rolfyone rolfyone left a comment

Choose a reason for hiding this comment

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

we can probably deprecate the v1 peers if we do add this, and should add to changes list :)

@arnetheduck
Copy link
Contributor

This feels like a lot of bother for a small aesthetic nuisance in a fringe interface..

@dapplion
Copy link
Member Author

This feels like a lot of bother for a small aesthetic nuisance in a fringe interface..

Also true, taking the counter argument there's really no harm in sticking with this oddity that already handled by all implementations.

@nflaig
Copy link
Member

nflaig commented Dec 11, 2023

It is an outlier and hence needs some special handling during parsing if you implement a generic http client/server. It's a minor thing but probably not wrong to get rid of technical debt.

@rolfyone
Copy link
Contributor

Sounds like maybe we close the issue as 'won't fix'?

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.

Inconsistency in /eth/v1/node/peers
4 participants