refactor: rename modules to consist with the primary export#562
Conversation
You are not enabling case sensitivity on Windows for git folders? 😉 Not but apart from joking I agree with you, if you have modules with default exports they should be called the same. I think we use both mixed in our code base, but slightly I would prefer CamelCase as we do for components etc |
I develop on a remote Linux server for everything (except for Talk Desktop when doing desktop parts) 👀 |
susnux
left a comment
There was a problem hiding this comment.
except for the one import this is fine
Signed-off-by: Grigorii K. Shartsev <[email protected]>
3d48927 to
9663b13
Compare
Fixed |
Maybe a very personal opinion, but I'd expect a file to have the same name (incl. casing) as the primary export in the module.
Especially to avoid errors from case-insensitive OS (Windows) (though it is handled by ESLint).
Alternative:
kebab-case