Filenames should be consistent with a styleguide rule

[Bargs]

The current styleguide doesn't explicitly define a filename format. A PR to close this issue should include an addition to the styleguide and a cleanup of existing filenames.

Previous debate was over camelCase vs. snake_case

For snake_case:

• most existing filenames and directories are snake_case
• The current style guide implies snake_case is correct
• node_modules and bower_components are both snake case

For camelCase:

• Maps more directly to variable names e.g.:

import SomeClass from './SomeClass';
import someFunction from './someFunction';

[w33ble]

I'll echo what I assume I've said before, possibly multiple times (but thanks for creating a formal issue about it).

I'm partial to snake_case naming, since it's more common in the JS ecosystem and it's what we've mostly used so far. However, as long as we are consistent, I honestly do not care.

[spalger]

I strongly prefer camelCase and am willing to do the work to transition the code base.

I am want camelCase because there is no good reason to use two capitalization styles. If we used snake_case variable names I would prefer snake_case file names. We don't. Let's be consistent and use camelCase everywhere! 🎉

🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫 🐫

[Bargs]

I'm also a fan of the 🐫

Just today I found myself trying to name an exported function with 🐍 to match its filename, and eslint rapped me across the knuckles.

[kimjoar]

🐫s all the way!

I've started mapping filenames directly to my default export. I just find it easier to read and work with.

[epixa]

I vote for the exact naming conventions in the airbnb styleguide: https://github.com/airbnb/javascript#22.6

So:

• PascalCase.js for files that export a single class or an object literal
• camelCase.js for files that export a function

[w33ble]

PascalCase.js for files that export a single class or an object literal
camelCase.js for files that export a function

If we're doing camel, I kind of like this in principle, but I can see it becoming a problem on OS's that are loose with case (Windows and most people on Mac, so almost everyone). Renaming that file becomes a pain, requiring you to rename it to something completely different, check in the "remove" to git, then rename it back to the case you actually want...

[spalger]

@rashidkpc has settled this, we're moving all filenames to snake_case.