If our custom scss files start with an "_" should our JS ones also start with "_"?

[palewire]

If our custom scss files start with an "_" should our JS ones also start with "_"?

[emamd]

I don’t think it’s necessary. As far as I know it’s a convention with SASS but not w JS. Might not even be a convention with SASS just how I learned to do it 🤔

…

Sent from my iPhone

On Feb 25, 2018, at 7:51 PM, Ben Welsh ***@***.***> wrote: — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[palewire]

It seems a little weird to me that the JS files don't have it. I propose that we add it there as well.

My read has always been that "_" prefix denotes that the file is "private" and will not ultimately be published to the live site (because it will be compiled into the main.js file when the site is baked.)

That private convention is generally followed elsewhere in Yeogurt with its folder names, like _scripts. And it's common in other programming languages, like Python's private methods.

[emamd]

I just tested it and the SASS files work either way. So I'm happy to have the convention be that child files have underscores in the name, or not.

The disadvantage is they won't always see files like this in the wild, the advantage is that it's a nice way to organize and designate child files, and I like how they get sent to the top of the files list in alphabetical sorting.

If we do it we should point out that they don't have to, but it's a nice convention.

[palewire]

Sounds good to me. Let's also remember to point out the underscored folders at some point when we walk the students through the folders created by Yeogurt.