Description
In 2020, localization is not an option anymore
It's a first-class feature that is required in almost every project.
I know that firebase is free, but still… I'm paying for services due to my usage.
I think this would be a great thing for both firebase platform and users to be able to translate this module correctly. You'll reach more developers and we would be even happier to build apps ;)
This is not something very hard I guess when we know the technical level of people like @CodingDoug @jenperson @ToddKerpelman and many others @ firebase (ping @nicolasgarnier).
Problem with current configuration
- Who is using UMD module in 2020 ?
I don't think many people keep using the UMD CDN build, most people build their app using react/vue or even angular… (I'm sorry WordPress users 😅)
Everything gets packaged in something like webpack or rollup… ES6 / CommonJS is a need.
- Build time configuration is not adaptative
If you have a multi-localized app, it's not scalable. You can't even simply update the lib to leverage patches.
Simple Solution
- Let the library close to what it is currently, with English shipped, so the firebase team has only one language to maintain.
- Give the opportunity to pass a localized object with keys/values at instantiation, like we have
signInFlow
currently, we could have atranslations
which will be dynamically injected by us, depending on any context.
I would be very happy to help with that, but I think It would be quicker for me to rework all of this with react-js due to the complexity of the code here Ahah 😅 But even though, I can help on some parts (@nicolasgarnier if you need some help on react)
Best wishes for this Christmas,
Andréas