Skip to content
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

Improvement idea: support object grouping #8

Open
NicolasDionB opened this issue Oct 28, 2019 · 2 comments
Open

Improvement idea: support object grouping #8

NicolasDionB opened this issue Oct 28, 2019 · 2 comments
Assignees

Comments

@NicolasDionB
Copy link

We've been using this package to manage our texts and really love the plural functions. The only problem I see is organizing your text definition. It's not an issue when you have only a few lines in your JSON file but as the projects gets bigger with more areas and topics in the app, it gets harder to stay organized.

As JSON doesn't allow comments, my idea would be to create objects in the definition itself and have texts in it. For instance:

{
    "screenSharing": {
        "title": "Screen sharing",
        "startError": "Another user is already sharing his screen."
    }
}

instead of:

{
    "screenSharing_title": "Screen sharing",
    "screenSharing_startError": "Another user is already sharing his screen."
}

That would make things so much easier to maintain. Hope this idea gets through!

@KingWu
Copy link
Owner

KingWu commented Oct 30, 2019

Interesting. Wanna to know your team to manage the text jsons directly?

For my use case, i use Airtable to manage my texts and share this table to translators.
That why i write another library - lang_table to generate different json from airtable

Basically, i will not manage the jsons file directly.

@NicolasDionB
Copy link
Author

I hear you. I've seen Airtable but to use it on a larger project with multiple devs, I don't want to rely on yet another online service for managing this. Any chance of improving this?

@KingWu KingWu added enhancement New feature or request feature-request and removed enhancement New feature or request labels Dec 2, 2019
@KingWu KingWu self-assigned this Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants