Read the statement by Michael Teeuw here.
Is it possible to have custom information for each module in the config file?
-
In order to improve the usability of my page system, I would like to be able to use a custom piece of information in the config file to define pages and positions for the Modules.
{ "module": "clock", "position": "top_right", "pages": {"pageName": "position"}, "config": {} }However, it seems just using getModules.enumerate() doesn’t supply that new pages object.
As a workaround, I noticed that the config for each module is given and so the page’s object could be stored inside that. However, for less confusing use, I would rather have it outside.
The other option I would explore is simply importing the config into my node_helper and then parsing the config manually, but before I went ahead with the plan I wanted to see if there is some reason to refrain from that.Is there a correct way to do this? Is it correct to do this at all?
-
After trying out the method of importing the config, it works well and seems to be stable. If anyone has any reason why not to require the config.js in a node_helper file, I would appreciate an explanation.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login