Manage locals with same key about lib HOT 3 OPEN

After checking a bit, I think we should disallow not setting any key / setting an empty string.
The key is used to check if we should load the translation file. It can cause existing translations to be loaded on direct access and not during client-side navigation. (I can provide an example project if necessary)

As an alternative for my use case, I think we could provide a way to disable the automatic dot notation (I can create a separate issue to discuss that).

We should, however, still provide a way to manage the same key problem exposed here.

from lib.

Hi @ThibaultAndreis!
Thanks for your great point for a discussion.
I’m wondering if we could use config.preprocess allowing to use an object instead of string..
For example:

{
    preprocess: {
        strategy: 'full',
        identicalKeys: 'merge'
    }
}

from lib.

This seems like a logical modification to me, but it may require implementing it as a major release to respect semantic versioning and avoid disrupting other people's workflows.

We could make it this way, or just add the new code for now, without changing preprocess, limiting potential breakage to only the new code.

We can still make changes in a future release, if necessary. However, it might require more users to modify their configurations in the end.

How do you think we should pass the value of 'identicalKeys' to the serialization function?

Edit : If we include the change preventing from using empty keys, it would be a breaking change, so we can modify the config anyway I think

from lib.