Went ahead and made a "fix" for issue #186. Since users place authentication information into settings.json, this adds that file to .gitignore so it doesn't get pulled in with commits if people are contributing. To be able to still work on the base/example file, though, it's renamed as settings.example.json and the user is asked to first copy it to settings.json (the same way that options.js is handled in the main echo-sonos folder).
Just something small that I thought of while working on my fork locally. Deny if it's unnecessary or too much extra inconvenience on the end users' part.
Went ahead and made a "fix" for issue #186. Since users place authentication information into settings.json, this adds that file to .gitignore so it doesn't get pulled in with commits if people are contributing. To be able to still work on the base/example file, though, it's renamed as settings.example.json and the user is asked to first copy it to settings.json (the same way that options.js is handled in the main echo-sonos folder).
Just something small that I thought of while working on my fork locally. Deny if it's unnecessary or too much extra inconvenience on the end users' part.