File name BEFORE the Warning & full path

[kkmuffme]

It would be great if the i18n could include the full path to the files in Warnings & also put the file first, as this is more common among tools (eslint, php-cs-fixer,...) so easier to integrate into existing build pipelines.

Instead of this:

Warning: The string ""%s" added to cart" contains placeholders but has no "translators:" comment to clarify their meaning. (example.php:593)

we should see this:

/var/wp-content/plugins/example/example.php:593: Warning: The string ""%s" added to cart" contains placeholders but has no "translators:" comment to clarify their meaning.

Advantage:

• no need to change lots of build pipelines, bc the format is (almost) universal
• full path is better than only file name (especially when automating things)

[swissspidy]

Great suggestion, thanks! Totally makes sense.

I wanted to improve the audit part for some time now anyway, see #39.

[swissspidy]

Related: #167

[elenachavdarova]

Pull request: #361