-
Notifications
You must be signed in to change notification settings - Fork 865
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
fix: uppercase Discovery.MDNS.enabled in default config #1632
Conversation
@lidel do you think we should have ipfs desktop check for the incorrect key in the config, and remove it where it finds it? |
This cleans up configs of existing users As suggested in #1632 (comment) License: MIT Signed-off-by: Marcin Rataj <lidel@lidel.org>
Good question. Right now we only control the defaults applied on clean install. There is a need to have some generic way of migrating go-ipfs configs of existing users for things like @rafaelramalho19 @olizilla mind reviewing my changes? |
License: MIT Signed-off-by: Marcin Rataj <lidel@lidel.org>
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, but because I've added migrateConfig
would appreciate second set of eyes before merge
|
||
// Cleanup https://github.com/ipfs-shipyard/ipfs-desktop/issues/1631 | ||
if (config.Discovery && config.Discovery.MDNS && config.Discovery.MDNS.enabled) { | ||
config.Discovery.MDNS.Enabled = config.Discovery.MDNS.Enabled || true |
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.
Isn't this true
everytime?
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.
no, user could remove it or explicitly set it to false to disable noise in LAN
Merging to unblock #1638 |
Fixes #1631