Temporary disable modules

[paviro]

It would be great if one could add disabled: true to a modules dictionary to disable it without removing its configs. What do you think?

[yawns]

I like the idea, to quickly disable modules for testing purpose.

[paviro]

Yeah exactly just re added my facial recognition module but I could not get openCV working on Sierra yet so it’s crashing and I can’t disable it without removing the config again…

[KirAsh4]

I don’t remove config sections … I comment them out … If I’m going to edit that file to change a flag, it’s just as easy to add a /* ... */ tag around the specific section.

[paviro]

@KirAsh4 this does work inside a dictionary? Didn’t know that still I think an option would be cleaner @MichMich?

[KirAsh4]

> opens nearby dictionary, flips to ‘politics’, grabs red pen and writes /* ... */ around definition <

YEP! Still works!

I wasn’t referring to the actual module files. I’m talking simply editing the config.js file and comment the specific module’s config section out.

[MichMich]

Its just a js file. So you can use /* */. That’s what I do!

[roramirez]

Seem a good idea add the disabled option. In case is your write the config from other app or external system can be more cleaner add the config option instaed of commented block

Anyway, I pushed a PR for this https://github.com/MichMich/MagicMirror/pull/498

[Mitchfarino]

Couldn’t you just hide it with the RemoteControl?

[Jopyth]

@Mitchfarino This could be an option, however it only visually looks the same.

If for example a module temporarily does not work for some reason (blocks the start of the mirror), hiding it with the Remote-Control would not help.

What you probably wanted to say is: This should also be added to the Remote Control module. And I would like to include this option in the GUI for the config there. And there is a big advantage in a config option to disable a module (versus commenting out), since this leaves the values readable from other JS code, i.e. the Remote Control module.