andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix existing settings tests that did_you_mean broke.

Browse Source
This commit is contained in:
Thomas Adamcik 2012-09-01 12:15:08 +02:00
parent 03a7f03bb8
commit 4e4a209ec3
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
mopidy/utils/settings.py
View File

@ -199,6 +199,9 @@ def mask_value_if_secret(key, value):
def did_you_mean(setting, defaults): def did_you_mean(setting, defaults):
"""Suggest most likely setting based on levenshtein.""" """Suggest most likely setting based on levenshtein."""
if not defaults:
return None
candidates = [(levenshtein(setting, d), d) for d in defaults] candidates = [(levenshtein(setting, d), d) for d in defaults]
candidates.sort() candidates.sort()

2
tests/utils/settings_test.py
View File

@ -23,7 +23,7 @@ class ValidateSettingsTest(unittest.TestCase):
result = validate_settings(self.defaults, result = validate_settings(self.defaults,
{'MPD_SERVER_HOSTNMAE': '127.0.0.1'}) {'MPD_SERVER_HOSTNMAE': '127.0.0.1'})
self.assertEqual(result['MPD_SERVER_HOSTNMAE'], self.assertEqual(result['MPD_SERVER_HOSTNMAE'],
u'Unknown setting. Is it misspelled?') u'Unknown setting. Did you mean MPD_SERVER_HOSTNAME?')
def test_not_renamed_setting_returns_error(self): def test_not_renamed_setting_returns_error(self):
result = validate_settings(self.defaults, result = validate_settings(self.defaults,