-
Notifications
You must be signed in to change notification settings - Fork 46
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
Redo gconf #503
Redo gconf #503
Conversation
There is one test failing that I cannot figure out. I have spend a lot of time on fixing tests and I cannot figure this one out.
|
Closed in favour of https://github.com/iov-one/weave/compare/gconf_alex_spike?expand=1 |
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.
Nice start. This is actually my preferred approach.
I think a bit more polish and I would give it a 👍
Will add comments/examples about polish
I'm reopening this one, as I used it as a basis for my new pr #534 Let's get this done |
This comment has been minimized.
This comment has been minimized.
Cleanup `gconf` package configuration. Instead of allowing for any key-value pairs inserted into gconf store, require each module to use a custom protobuf configuration object that will be stored and retrieved with the help of `gconf` package. resolve #456
- enhance error messages - move message code to `msg.go` - move handler code to `handlers.go` - register configuration handler together with other message handlers
aff60d3
to
4fe62e9
Compare
I think this is ready. @alpe @ethanfrey please review it again. 🤞 |
Will review now |
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.
Looks good, but please fix broken benchmarks before merging
// message must be signed by an owner in order to be authorized to apply the | ||
// change. | ||
type OwnedConfig interface { | ||
Unmarshaler |
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 think referring to Configuration
here is cleaner. It shows we extend the Configuration interface with one more method
🎉 🎉 |
Cleanup
gconf
package configuration.Instead of allowing for any key-value pairs inserted into gconf store,
require each module to use a custom protobuf configuration object that
will be stored and retrieved with the help of
gconf
package.resolve #456