Config Error

lavolp3

@sdetweil Looking at above post, there’s looots of errors in the config.

@PHAGE-GOV we can’t lead you through all of these.
You need to understand how config.js needs to look. Only one comma set false or forgotten breaks the whole file and the mirror.

lavolp3

@lavolp3 The alert part needs to look like this:

		{
			module: "alert",
			position: "right",
			welcome_message: "a string"
		},

PHAGE.GOV

@sdetweil okay so ive been combing through the code, and since i didnt know how to properly edit .json files, i had alot of cleanup to do, im still not done, but getting there. what is a trailing space though? i dont know what to remove

PHAGE.GOV

@lavolp3

{
			module: "compliments",
			position: "lower_third",
			compliments: {	
				"anytime" : [
					"Hey there sexy!"
				],
				"morning" : [

so 64 is the compliments line and it says it has trailing spaces. Im actually learning so much about json files rn so thank you @sdetweil and @lavolp3

sdetweil

@PHAGE-GOV ignore the trailing space error. It’s stupid

PHAGE.GOV

@sdetweil indeed it is, i found it tho, and i fixed everything else too! thank you so much! and i learned so much from this also, i feel much more confident poking around and i defs learned much more about proper coding

sdetweil

@PHAGE-GOV and finding your way on the next error. After 3 years I still make them

PHAGE.GOV

@sdetweil yeah, but npm run config:check was such a life saver

BKeyport

one of the biggest tips I can give you is to throw out everything you know about capitalization…
Welcome_message is different from welcome_message

Most of the time, with RARE exception, the initial letter is lowercase. javacriptIsWeird

sdetweil

@BKeyport no… it is entirely up to the author of the module what case is used.
there are no rules…

only thing is javascript is case sensitive

var foo
is different than
var fOo
etc…

the config code doesn’t care, it takes all the settings and makes an object
the module then looks for specific items… almost NEVER checking for case mismatch

config.foo
will NOT find
config.fOo

it is NOT an error to config if fOo is not present.

filenames on linux are also case sensitive