New configuration Feature: moduleConfig

[bugsounet]

moduleConfig

it's allows to set module config from another config file in module config folder

sample for calendar:

{
  module: "calendar",
  header: "US Holidays",
  position: "top_left",
  moduleConfig: "config.js"
}

if moduleConfig is defined, it will look for the defined config in the module's config folder

sample remote config file in calendar/config/config.js:

const config = {
  calendars: [
    {
      fetchInterval: 7 * 24 * 60 * 60 * 1000,
      symbol: "calendar-check",
      url: "https://ics.calendarlabs.com/76/mm3137/US_Holidays.ics"
    }
  ]
};

module.exports = config;

Todo:

• add it in test suite

[bugsounet]

@rejas, @khassel : can i have a review at this state, thx guys

[KristjanESPERANTO]

Interesting, but what is the use case here? 🙂

[bugsounet]

• avoid having a very very heavy MM² config file
• allows you to find your (final) config more quickly
• allows to create multi-config (exemple: multi instance configs, test config,...)

[sdetweil]

i don't understand any of those use case words

[bugsounet]

@sdetweil : ok, should i close it so ?

[sdetweil]

maybe you could give some practical examples how this solves whatever problem you see

i dont see any reduction in config info. just moving it from one place to another

[bugsounet]

maybe you could give some practical examples how this solves whatever problem you see

hey, there is no problem... it's not an issue!
it's just a PR

i dont see any reduction in config info. just moving it from one place to another

just there

What do you search really ?
Personally, I am looking to add features to MM²

[bugsounet]

In any case, it's only 2 days of coding and testing lost.

(I am frustrated)

Thx