-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typo case miss(mix)matching in modue name #271
Comments
Why is this a problem after so many years? |
it's anyway |
its called don´t be lazy around here whats up. i18next-browser-languageDetector is dangling fix it to to much better to read and understand and these are 2 seperate words as you intend in cour camelCasing 🐪 so please fix it up and use what the whole internet preffesed snake-case @adrai im see it only right now and im the qa guy in our team. i see what other people dont (want to see) |
-> i18next so naming makes sense i18next-http-backend |
same also for: i18next-{type}-postProcessor |
beside that JS uses camelCase mostly...not snake_case |
would put a high burden on all other devs having to update their dependencies to new module...(which most won't even notice -> as it's not a automatic ncu -u) |
i18next-browser-languagedetector
i18next-browser-language-detector
snake-case is desired case and most common in all projects almost.
its kind of easy to migrate: simply deprecate this repo and switch to a new c&p version with a new name.
The text was updated successfully, but these errors were encountered: