ofcyln / i18n-json-to-xlsx-converter

i18n JSON to XLSX Converter is a CLI tool runs in a terminal, and helps you to convert a JSON file(s) to EXCEL sheet(s) including keys column defined as nested with dot notation, and the values column for those keys. Also, the CLI tool converts an EXCEL sheet to JSON file(s) by considering its values columns as individual files.

Hi there, I'm Osman 👋

🌌 About Me

• I am a highly motivated and experienced Front-End Developer with over ten years of expertise in web and mobile application development. My passion lies in creating websites and mobile apps that grab people's attention and engage users. I have a strong desire for continuous learning, allowing me to quickly adapt to new technologies and deliver exceptional user experiences. In the fast-paced world of digital technology, I stay updated with the latest trends and changes, ensuring that my work remains current and relevant. I am dedicated to writing clear and efficient code, which not only enhances my own productivity but also enables seamless collaboration within diverse teams.

🌟 Notable Projects

• Save the Text: Keep your copied text, and clear formatting of the copied text
• Mortgage Expense Calculator: Calculate mortgage expense in the Netherlands
• Currency Exchange: Convert currencies easily
• i18n JSON to/from XLSX converter CLI tool: Generate i18n JSON files easily

Websites

• My Resume
• My LinkedIn profile

🔧 Skills

i18n-json-to-xlsx-converter's Issues

multiple json to single excel

You have a great feature to take a single excel and create multiple json lang files. I'd like the reverse. If I supply a list of multiple json files they should all be exported to a single excel with a column for each language. As opposed to producing a single excel for each json file. perhaps add a second flag for this behaviour to allow either or functionality would be great.

Wishes

1. I would like to manage file reading settings. Example readXLSXFile(filePath, { trim: false }), because by default trim is true.
2. I would like to generally use the flag either to use or not the library unflatten. Me not need this: unflatten(allLanguages[languageTitle], { object: true }).

Thanks

Empty cells rule

Hello,

Thanks a million for this wonderful tool. I've been looking for this for years, and it is so time-saving...

Just one enhancement that would be appreciated: if we add a new translation key in the Excel file, then all columns (except English for instance) are empty (until they get translated by agencies).
When converting to JSON, then the key value is set to null.
This strategy is preventing our app fallback strategy from working, meaning that if I switch my app to FR for instance, then the value displayed is also "null".

Could you add an option to the command in order to remove the key woth empty values from the JSON? This would allow the fallback strategy to work properly. Make it an option in case other projects needs to have the null value :)

What do you think?

The original array of objects ended up not being correctly reduced, but understood as objects.

Original in project

 "features": [
                {
                    "title": "Unlimited chatbots"
                },
                {
                    "title": "2,000,000 characters/month"
                }
]

Final restoration results

 "features": {
        "0": {
          "title": "Unlimited chatbots"
        },
        "1": {
          "title": "2,000,000 characters/month"
        }
}