Skip to content

Conversation

amadeann
Copy link
Contributor

@amadeann amadeann commented Jan 5, 2018

Laravel localization doesn't follow the usual "dot notation" for files in nested directories. When using the dot notation with nested directories translation key is returned.

Such edit to docs was suggested already in July 2016 (#14212).

Laravel localization doesn't follow the usual "dot notation" for files in nested directories. When using the dot notation with nested directories translation key is returned. 

Such edit to docs was suggested already in July 2016 ([#14212](laravel/framework#14212)).
@taylorotwell
Copy link
Member

This behavior is not intentional and thus may not be supported in the future so would rather not document it.

@timo75
Copy link

timo75 commented Aug 19, 2020

This behavior is not intentional

You mean localization files should not be placed in nested directories? Or are you referring to slash vs dot notation when linking them?

@StefanoTesla
Copy link

What in laravel 10?? We can use subfolder for translations or not??

@vsjoshtait
Copy link

With reference to laravel/ideas#2629, the fact that this behaviour currently works with / notation means that a decision should be made either way.

It would be trivial to officially support dot notation for nested folders. Doing so will allow developers to keep translation files smaller and have a closer parity between front-end components and their strings, not to mention greater flexibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants