[11.x] Unexpected behavior in `Illuminate\Translation\Translator`'s `get()` method about framework

[crynobone]

Unless I am missing something, it is not clear if this is expected behavior.

This is the expected behavior and described in the documentation: https://laravel.com/docs/11.x/localization#using-translation-strings-as-keys

JSON translations were never meant to work exactly the same as PHP translations.

[saadsidqui]

@crynobone

JSON translations were never meant to work exactly the same as PHP translations.

I'm aware. I fail to see in the docs where it says a key for which a translation is explicitly defined, would return the key. i.e.:

// en.json
    ...
    "empty": "",
    "zero": "0",
    ...

// in a PHP file
__("empty") // returns "empty"
__("zero") // returns "zero"

Maybe the docs should mention these edge cases.

Thank you.

[crynobone]

Feel free to send a PR to the documentation.