paulg
paulg
1. centralise it for easy to maintenance is a good common practise. otherwise, when we add/modify a section or item, we have to go through many files. multi language files...
there are a few PR related on language setting. If we use one json file for multiply languages. this will be not a issue anymore. :)
> @cove9988 If we combine all the languages into one file, wouldn't that potentially create really messy merge conflicts? No, there is no messy merge, it's clean cut with same...
okay, still keep multi-language files with most people agreed. 1. use DEFAULT_LANGUAGE environment var to change language setting. 2. add test cases.
Sure, I'd be happy to. Please provide your github link. Best regards Paul On Wed, 1 Feb 2023, 08:41 Makovez, ***@***.***> wrote: > Hi, we are working on a similar...
I just did. On Wed, 1 Feb 2023, 11:24 Makovez, ***@***.***> wrote: > Can you text me on telegram @sbongown > > — > Reply to this email directly, view...
check your log report at /outputs/latestdate-time/reports. mostly the llm was not working...