You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Config file with self.config in skills will end with the 19.08 release. Change so that it uses another file if users don't want to use home. The file will be ~/.mycroft/email-skill/email.yml. I will use yaml.
Before 19.08:
Define self.config in the skill.
In the Longer Run:
Change code to use YAML file, over home settings, if existent.
Keep backwards compatibility with Config file
I might want to have the skill say if the user is using the old config file something like: You are using the old version of configuring the skill on the device. Please go to [insert url here] to learn more.
Update docs
Change the config file to the yaml file
Create a "moving" page which user will land on when directed by the skill (see above)
Promote change.
The text was updated successfully, but these errors were encountered:
Found that I could get around this with the Mycroft Config. just define self.config My self. However, I should just switch it to yaml because its is nicer.
I'm going to keep the bug label on this issue until I define self.config in the skill.
LinusSkucas
changed the title
Discontinue use of config file
Change use of Mycroft JSON config file to a skill-only YAML configuration file
Mar 9, 2019
Hi @JonahEmbry The skill has been updated to fix this problem, and has been submitted to the market place for review. Once it is accepted, you should use the new docs to configure the skill. Alternatively, just using the home.mycroft.ai settings has been verified to work.
Using Config file with self.config in skills will end with the 19.08 release. Change so that it uses another file if users don't want to use home. The file will be ~/.mycroft/email-skill/email.yml. I will use yaml.
Before 19.08:
self.config
in the skill.In the Longer Run:
Change code to use YAML file, over home settings, if existent.
Keep backwards compatibility with Config file
Update docs
Promote change.
The text was updated successfully, but these errors were encountered: