Closed robozman closed 6 years ago
That sounds good and should be extremely easy since it would just be a rename. Visplay.config doesn't have support for anything but sources.
Great! I think it will also make https://github.com/ColoradoSchoolOfMines/visplay/issues/5 easier as we will not have to worry about ignoring non source related settings when obtained recursivly.
Requirements
I'm breaking visplay,yaml into config.yaml and sources.yaml. Better naming imo
@jhgarner The README needs to be updated to your new config syntax
This seems to be finished. We have settled on main entrypoint config.yaml, and sources.yaml files that can point to assets/playlists.yaml and import other sources.
I think it would be a good idea to break up visplay.yaml into visplay.yaml, for general configuration and sources.yaml for locations of assets/sources/playlists.yaml.
Thoughts?