Lint and fix textdomain and usage in PHP files in plugins and themes. 

time

wp-textdomain

  "description": "Lint and fix textdomain and usage in PHP files in plugins and themes.",

  "repository": "https://github.com/timelsass/wp-textdomain",

Typical usage is done during a build process for plugins or themes.  This code shows how to add linting on your php files, and output the results to console:

const wpTextdomain = require( 'wp-textdomain'

const wpTextdomain = require( 'wp-textdomain' );

 Alternatively, you can pass the configuration option to automatically fix the issues found during the linting report:

In some cases, you might need more than one textdomain while linting files to be checked against.  A common use case for this is by including a framework, such as Kirki, in a theme which does supply it's own translations:

When using the fix option, only errors found that aren't `kirki` are fixed.  When fixing errors, the first textdomain listed is the one used as the primary textdomain.

`pattern`: **String** A [glob pattern](https://www.npmjs.com/package/glob) for matching files.

`options`: **Object** wp-textdomain configuration options.

**String/Array** Textdomain(s) to lint and fix.

If a string is passed, this will be the textdomain that is used to compare against in linting. When passing an array of textdomains, all are checked against as valid textdomains to be used in a theme or plugin.

When running wp-textdomain with the fix option set, the first textdomain in the array is used as the primary textdomain that is used to replace or be added to gettext calls missing or with alternate textdomains.

**Bool** Whether or not to write files with fixes applied.

When using the fix option, errors that are found are fixed using the first textdomain listed.

**Object** [php-parser](https://www.npmjs.com/package/php-parser) configuration options.

**Bool** Whether or not to perform lints/fixes against gettext methods that are missing textdomains.

**Bool** Whether or not to perform lints/fixes against gettext methods that are using a variable instead of a string in the textdomain field.

**Array** A pattern list of strings containing available gettext methods, and argument positions.

**Object** Configuration options for calls made to [fs.readFileSync](https://nodejs.org/api/fs.html#fs_fs_readfilesync_path_options).

**Object** [minimatch/glob](https://www.npmjs.com/package/glob#options) configuration options to pass in.

**Bool** Option to force build fails by exiting process or just warn in console on error.

**Object** Logfile configuration options.

- `format` **Object** Filename output format.

	- `prefix` **String** String to prepend at beginning of filename.

		{
		"name": "wp-textdomain",
		"version": "1.0.0",
		"version": "1.0.1",
		"description": "Lint and fix textdomain and usage in PHP files in plugins and themes.",
		@@ -5,0 +5,0 @@ "main": "index.js",

		@@ -25,3 +25,3 @@ # wp-textdomain
		```js
		const wpTextdomain = require( 'wp-textdomain'
		const wpTextdomain = require( 'wp-textdomain' );

		@@ -28,0 +28,0 @@ wpTextdomain( '*/.php', {

Improved metrics