-
Notifications
You must be signed in to change notification settings - Fork 783
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
Update devp2p
API methods
#2872
Comments
One note: this is very well breaking though, so this should be done relatively imminently after RC1 so that we can get it into the final releases. |
Hi Amir, So to expand a bit on the initial description: the Update: I am now looking a bit into this. For I would in turn add the following to the issue: in This can very likely not be done in just one go but will likely need some one-by-one approach (or 2-4 at once or so) and then re-running tests (or better: CI with client) re-occuringly, otherwise one runs the risk to "guard" too many properties at once and have things breaking on various fronts since properties are accessed anyhow. If properties are only accessed by tests please do not make public but rather access by For the EventEmitter thing (might make sense to do in a separte PR now with the above task expanded): So there is also an example in #2857 as well on this. For These classes should instead get an additional (public) property So Likely also good to do a one-by-one approach here, there is a lot of event-listening in the client and there things might break otherwise. Or minimally client tests should be run every now and then I guess. |
We should upgrade
devp2p
s' API to match changes done in the other packages_common
tocommon
on any/all classes exposed by Devp2p (notablyRLPx
)EventEmitter
class to have an internalevents
property instead so the main class API isn't cluttered up withEventEmitter
propertiesThe text was updated successfully, but these errors were encountered: