After publish file takes another array format

I mean i have in files lines like so:

    'account.user' => '/user',
    'account.user.step.two' => '/user-step-2',
    'account.user.step.three' => '/user-step-3',

In DB all lines are stored. But after publish it the file looks like:

   'account' => [
        'user' => [
            'step' => [
                'two' => '/user-step-2',
                'three' => '/user-step-3'
            ]
        ]
    ],

And in this time my first line goes lost. Is there any config that do the thing and export/publish key-value from DB in another format? #

[vsch]

@gerardreches, the dot notation by convention is used to separate arrays. The issue is that on publishing the dot convention is always interpreted as array convention. The code to ignore the array convention when a key has a value assigned that would be overwritten by an array gets to be convoluted.

Would it be possible for you to use another delimiter than a period . so it does not conflict with the translation array notation, for example a dash - would do the trick.

[gerardreches]

@vsch I’m in the same problem right now.

I have some translations for routes. One of these routes (/services) is for a services page, so I called the string routes.services. The thing is that the services page is a top level for the different services:

/services/testimonials /services/transactions /services/estate and more… So the strings are routes.services.testimonials, routes.services.transactions, routes.services.estate, and so on.

When I publish the routes group, it shows me

Incorrect use of dot convention for translation keys (value will be overwritten with an array of child values): routes:: services

and my laravel project shows a trim() error until I delete the generated translations.

I know that this is logic, because there are two equal keys with different values: one contains a string, and the other contains an array.

Is there some workaround for this? Or the only option is to rename the routes.services key?