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/ww_cfg #207
fix/ww_cfg #207
Conversation
handle naming collisions due to white space and underscore differences handle "active" flag based on the concept of "main wake word", compatible with the mycroft way and expectations, multiple wake words will require explicitly setting "active": True in config from now on fix possible iteration bug on stop
Codecov Report
@@ Coverage Diff @@
## dev #207 +/- ##
==========================================
+ Coverage 50.35% 54.17% +3.82%
==========================================
Files 119 156 +37
Lines 10077 9733 -344
==========================================
+ Hits 5074 5273 +199
+ Misses 5003 4460 -543
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
| # normalization step to avoid naming collisions | ||
| # TODO - move this to ovos_config package, on changes to the hotwords section this should be enforced directly | ||
| # this approach does not fully solve the issue, config merging may be messed up | ||
| word = word.replace(" ", "_") |
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.
@NeonDaniel a bit out of scope but related, should we enforce this in every key for mycroft.conf, not only for hotwords?
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 agree its out of scope.. My main concern would be breaking compatibility with plugin config; maybe we could log warnings about it in ovos_config and then remove it when we release 1.0.0 there?
handle naming collisions due to white space and underscore differences
handle "active" flag based on the concept of "main wake word", compatible with the mycroft way and expectations, multiple wake words will require explicitly setting "active": True in config from now on
fix possible iteration bug on stop