-
Notifications
You must be signed in to change notification settings - Fork 971
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
node: use Repository on the Node and slightly improve testing utilites #94
Conversation
…l them in one place and (2)make them importable. Unfortunately those testing functions will be part of the build
…ests; remove old in-memory Datastore and put ConfigLoader in the Node instead of just Config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really get why we need the LoadConfig
stuff - makes things more complicated for no reason. Let's just load the config during initialisation and store the pointer to the config on the Node please. I really want the Node init logic to be as clear and possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Co-authored-by: rene <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - resolved in sync w @Wondertan
Context
This is the last TODO of #86.
Changes
node
andcore
packages into testing.go