@Volkae Please try my fork:
git clone https://github.com/KristjanESPERANTO/MMM-DBF
Let me know if it runs more stable.
@Volkae Please try my fork:
git clone https://github.com/KristjanESPERANTO/MMM-DBF
Let me know if it runs more stable.
@MMRIZE Okay 😀 I just added it to the list.
@dcazman said in MMM-OpenWeatherForecast Error 401:
I think this is the fork I used.
According to your first post (output of git remote -v) you use the repository of jclarke0000.
@mumblebaj Many thanks for the tips! :smiley:
I have meanwhile written to the operators of the website to see if they can offer an API. If not, I will probably follow your suggested approach.
The maintainer is working on implementing the new API: https://github.com/fewieden/MMM-NHL/pull/51
So I see two options for you:
I’ve done it! 🥳 Checkout https://forum.magicmirror.builders/topic/19133/mmm-forum.
For accessing the read(-only) api you can use a cookie from your browser, e.g.
@karsten13 Thank you! That was the hint that led me to the solution 🙏
@bworch git status and git diff may help you 🙂
for MagicMirror purposes, is there a preferred style to be used for modules?
@kayakbabe I agree with Sam, but here’s a more detailed answer anyway: This depends on where you are. In some modules there are no rules for this - there and in your own modules it is, as Sam says, up to you.
However, to avoid poor code style, such as spaghetti code and inconsistently formatted code, which not only make maintenance and further development more difficult, but also affect team collaboration, many projects use static code analysis tools such as prettier and ESLint for checking code quality.
In the MagicMirror core (and with this in the default modules), we use the ESLint object-shorthand rule (see https://archive.eslint.org/docs/rules/object-shorthand) to ensure that only the shorthand version is used.
Since 6.14.12 there have been a lot of bug fixes, so an upgrade is recommended. And MM works fine with 8.19.2.