0.6

[MimoGraphix]

• When a new key found by user URL is logged while creating.
• Possibility to ignore JSON translation entirely
• Updated translation:find command
  • more specific regex
  • recognizing and logging variables from source code trans('something.something', ['variable' => $var1] )
  • location in the source is logged and displayed to a user
  • optional warning system when a key was not found in source code
• Possibility to ignore all newly found keys by a user (for production)
• index.php converted to blades
• New editing view with focus only on one specific translation with additional details ( variables, URLs, source locations )

[Slubby]

Heyy man

great job you've done here. But i noticed if you use:

trans_choice('user.name.age', $years, ['name' => Sam])

Then it will not see the variables.

But great job.

[MimoGraphix]

Heyy man

great job you've done here. But I noticed if you use:

trans_choice('user.name.age', $years, ['name' => Sam])

Then it will not see the variables.

But great job.

Hi @Slubby,
Thank you for your appreciation.

Sadly I was not able to put this into regex without splitting it into two different regexes and making it unnecessarily complicated.
But there is a feature (workaround) for these kinds of situations, variables in trans_choice() /trans() / ... are saved to the database also on the FE side.
Basically, every time user sees a "translation key" on the FE, method ->notifyMissingKeys() also writes variables into the database(even if "translation key" already exists in DB), this handles situations where variables were put dynamically with some method or they are declared as an array somewhere else in the code.

Hope this helps.

[MimoGraphix]

• Search option has been added, now it is possible to search by translations by key or value within all groups.
• Possibility to activate debug mode in configuration. After every translation will be placed original key in square brackets e.g.: trans('auth.login') -> Login [auth.login]
  NOTE: only when translation exists!