typo case miss(mix)matching in modue name about i18next-browser-languagedetector HOT 7 CLOSED

Why is this a problem after so many years?

from i18next-browser-languagedetector.

it's anyway i18next-specific implementation-pluginType nothing todo with casing

from i18next-browser-languagedetector.

its called
"i18next-http-backend": "2.0.2",
and not
"i18next-httpbackend": "2.0.2",
or
"i18next-httpBackend": "2.0.2",

don´t be lazy around here whats up.

i18next-browser-languageDetector is dangling fix it to
i18next-browser-language-detector

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)

from i18next-browser-languagedetector.

i18next-http-backend

-> i18next
-> http (using http, request, fetch, ...)
-> backend (is the plugin type)

so naming makes sense

i18next-http-backend
i18next-redis-backend
i18next-mongodb-backend
i18next-fs-backend
i18next-localstorage-backend
...

from i18next-browser-languagedetector.

same also for:

i18next-{type}-postProcessor

from i18next-browser-languagedetector.

beside that JS uses camelCase mostly...not snake_case

from i18next-browser-languagedetector.

its kind of easy to migrate: simply deprecate this repo and switch to a new c&p version with a new name

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)

from i18next-browser-languagedetector.