Config Error

[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

[BKeyport]

@sdetweil That’s effectively what I said… I’m working from within the naming conventions typically used by module authors, including myself, and trying to stress that case is important, because if you come from a world where it’s not (DOS/Windows, perhaps?) it takes some getting used to.

bottom line, Welcome_message is not the same as welcome_message

[sdetweil]

@BKeyport said in Config Error:

I’m working from within the naming conventions typically used by module authors

i didn’t know there were any conventions! least I don’t follow anything written anywhere

[evroom]

@sdetweil said in Config Error:

i didn’t know there were any conventions! least I don’t follow anything written anywhere

Naming conventions are not must, but it is used to make code more readable and understandable.
A quick google came up with this useful page:

https://github.com/ktaranov/naming-convention/blob/master/JavaScript Name and Coding Conventions.md

[sdetweil]

@evroom i have been coding for 45 years… i know what they are and know what good ones produce…

however, specific casing has always been a useless conversation…

make names meaningful, use case where appropriate…
i don’t follow camelcase, or any other std.