I had the idea to checking process development of a module and I created one to show images from a directory.
This module has a lot development stuff’s in files that I think should have a module. Is missing integration of test suite.
If you have any request to add it please let a message here or add an issue in Github.
I wrote a module to help developers to build your own modules.
This code include some examples and can be a quickstart. Included tasks to check code like is used in core by MagicMirror.
[card:roramirez/MagicMirror-Module-Template]
Let me know any suggestion.
Hey, new release
[1.2.0] - 2017-07-21
@strawberry-3.141 said in config error somewhere, need help:
https://twitter.com/roramirez/ status/843121280601669632
:)
This feature is include in the last release. Now you can use npm run config:check for check the configuration file :)
If you have troubles with range, IP, etc… Can set ipWhitelist: [] to allow all IP addresses.
Warning, this enables from everywhere (on your net) have access.
Hi everyone!
I’m working in a test suite for MagicMirror². I think is a good point to improvement more MagicMirror².
Now, the testing is doing manually and test suite can enable to test automatic features, fixes or prevent something is broker for a change introduced.
The project is bigger every day, its I really like it. Many contribuitors include proposals and new change every day. Some stats
Beeetwen the release 2.0.5 to 2.1.0 was
74 files changed, 3288 insertions(+), 755 deletions(-)
and pushed 257 commits around 2.8 commits per day.
I’m looking ideas, pushed or if someone is interested to collaborated. Maybe Trello, this forum or other method can be organizated the work.
Is already pushed the init work https://github.com/MichMich/MagicMirror/pull/623 This propused Mocha, a test Javascript framework working on Node.js.
The first way to do this is elaborate a list of test to develop.
I would like hear your comments.
@roramirez Sorry for all this. This was my mistake. I really pissed off with my confuse with options. The option in module configuration is OK but in readme is wrong.
Your Pull Request @Mykle1 is ready merged. Thanks.
Is missing body-parser lib required by MMM-Remote-Control
Go the module directory and run npm install
cd /home/pi/MagicMirror/modules/MMM-Remote-Control/
npm install
Yay! After a long fight the test are passing in Travis CI
I been working a little pice of work for that. You can check
https://github.com/roramirez/MagicMirror-Module-Template
Hola!, que error te da especificamente?
Saludos!
@jfisher446 You can add new test inside of testsuite for own module.
Creo que lo oportuno aquí es que alguien tome la iniciativa y cree el canal, luego publique y trata de mantener ese medio.
PS: Por mi, no tengo el tiempo de poder administrar el canal. Saludos!
@Sandy2503 said in After update to Mirror to 2.1.3 - no working Whitlist:
What do i have to do ???
Set the IP address of your MagicMirror there.
That happens because the release 2.1.3 was introduced a new change to make more secure the MagicMirror, to prevent open all interfaces to world. So, now from 2.1.3 the default values for address is localhost instead of 0.0.0.0… so …be careful to set this value.
So nice work guys! If somebody else can merge your changes with my PR or pushed other PR with theses changes go ahead.
I’ll prefer to keep the same behavior if API not get 401
@QNimbus I sent you the invitation
Well… Yesterday I submitted a patch to hack the situation with the new accounts in OpenWeather.
If you can test it will be great!
https://github.com/roramirez/MagicMirror/commit/e8438d37d78acc7a9e29e694a6987ce068324bcd
@B3nihana Please, use a develop branch or apply the patch https://github.com/MichMich/MagicMirror/commit/a7297d2685f5ed9b6b34df496065f05ee0d36568#diff-9d4f93dd73c92e4e5730a5c2e0146ad4L33