We should make i18n-node much stricter.

1. We can set custom objectNotation character, . by default. For example we can set : character, but this character sets default values.
2. With objectNotation we still can use __("Simple sentence with dot.") (https://github.com/mashpie/i18n-node/pull/210, https://github.com/mashpie/i18n-node/pull/235), but __("Simple sentence with dot. Try it") + ":" parsed as path.
3. With objectNotation __("Error: user not found.") parsed as “Error” key with default value " user not found." etc…

We have two ways:

1. Forbid using of whitespace with objectNotation. If string contains whitespace - skip handling it as path.
2. Leave all as is, but add mixedMode option to enable all from first point.

We should talk about it and decide which way we should choose. And i can help with implementation.

[oliversalzburg]

Then I don’t understand why this ticket calls for making i18n more strict. It is very strict in that it supports either format. Mixing formats would mean making it less strict.

[mashpie]

It might help to try multiple possible keys for finding. Example

__('Database Error: user not found.')

should 1st try to find the whole string Database Error: user not found. as key and stop or if none found also try Database Error as key.

    {
        "Validation.Error.Required": " %s is mandatory",
        "Database Error: user not found.": "Database Error: user not found."
    }

with json objects flattened internaly i18n would than also try a search for Validation.Error.Required: %s is mandatory and fail but next find Validation.Error.Required

This has to be tested carefully against all known use cases, though. And I still need a reasonable default for writing with updateFiles: true…