wp-pot / wp-pot-cli Goto Github PK

View Code? Open in Web Editor NEW

37.0 3.0 5.0 1.12 MB

Run wp-pot script via cli

License: MIT License

JavaScript 100.00%

pot wp-pot cli translator wordpress hacktoberfest

wp-pot-cli's Introduction

Generate pot file for WordPress plugins and themes

Like my work and want to say thanks?

Do it here:

Install

$ npm install --global wp-pot-cli

Usage

$ wp-pot --help

  Generate pot-files for WordPress localization

  Usage
    $ wp-pot <options>

  Options
    --bug-report, -b Header with URL for reporting translation bugs
    --comment-keyword, -c Comment keyword
    --dest-file, -o Destination file
    --domain, -d Domain to retrieve the translated text
    --last-translator, -l Name and email address of the last translator (ex: John Doe <[email protected]>)
    --no-file-paths, Don't write file paths to pot file
    --relative-to, -r Path to folder that file comments should be relative to
    --src, -s  Source files, multiple sources is allowed
    --team, -t Name and email address of the translation team (ex: Team <[email protected]>)
    --package, -p Package name
    --write-file, -w Write file

  Examples
    $ wp-pot --src 'src/*.php' --src 'extras/*.php'

gulp-wp-pot - Run wp-pot with gulp
wp-pot - API for this module

License

MIT © Rasmus Bengtsson

wp-pot-cli's People

Contributors

Stargazers

Watchers

Forkers

frozzare brandoncamenisch fossabot jakejackson1 iuriimattos2

wp-pot-cli's Issues

An in-range update of wp-pot is breaking the build 🚨

The dependency wp-pot was updated from `1.6.3` to `1.6.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

wp-pot is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.6.4

Update php-parser to version 3.0.0-prerelease.6
Add fixes to be compatible with new php-parser version

Commits

The new version differs by 15 commits.

10df9cc 1.6.4
3e2fa1d updates
1741d3e Merge pull request #55 from rasmusbe/greenkeeper/php-parser-3.0.0-prerelease.6
cd8b879 changes for php-parser 3
009babe chore(package): update lockfile package-lock.json
1f4754f fix(package): update php-parser to version 3.0.0-prerelease.6
61b0970 Merge pull request #54 from rasmusbe/rasmusbe-patch-1
7dd4655 Update readme.md
9af20c3 Merge pull request #53 from rasmusbe/greenkeeper/php-parser-3.0.0-prerelease.5
ec6b8eb chore(package): update lockfile package-lock.json
3c057bc fix(package): update php-parser to version 3.0.0-prerelease.5
5e04a4e Merge pull request #52 from rasmusbe/greenkeeper/php-parser-3.0.0-prerelease.4
3d9ffd6 chore(package): update lockfile
6e89aba fix(package): update php-parser to version 3.0.0-prerelease.4
14a988a travis fixes

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of wp-pot is breaking the build 🚨

Version 1.6.2 of wp-pot was just published.

Branch	Build failing 🚨
Dependency	wp-pot
Current Version	1.6.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

wp-pot is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes

v1.6.2

Updated dependencies for php-parser and matched

Commits

The new version differs by 4 commits.

fce4e65 1.6.2
92b29b3 Update deps
cd8d3a2 Merge pull request #43 from rasmusbe/dev-update
35e16c7 Updated dev packages and updated failed tests

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of wp-pot is breaking the build 🚨

Version 1.3.0 of wp-pot just got published.

Branch	Build failing 🚨
Dependency	wp-pot
Current Version	1.2.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

wp-pot is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 12 commits.

772eaed 1.3.0
a0a72f6 Add support for template name headers
c46b8cb Add support for metadata in file headers
76bba6b Keep comments when processing same line
140b364 Make headers function better
44b1b01 Improve code style
488cf04 Better looping in pot maker
22d5214 Split code into classes to improve code quality
e6ba169 Add tests for node 4 since its still maintained
6791e85 Set temporary path on travis to avoid failures
e0053ff Merge pull request #18 from rasmusbe/greenkeeper/eslint-plugin-node-5.0.0
a144c51 chore(package): update eslint-plugin-node to version 5.0.0

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

wp-pot : email in options causes script in package.json to fail

Describe the bug
I am using this Wordpress Plugin Boilerplate https://github.com/wp-strap/wordpress-plugin-boilerplate .

package.json has this translate script based on wp-pot:

"translate": "wp-pot --src '**/**/**/*.php' --dest-file 'languages/test-plugin.pot' --package 'test-plugin' --domain 'test-plugin' --last-translator 'Test Plugin <[email protected]>' --team 'Test Plugin <[email protected]>' --bug-report 'testplugin.com'"

When i run yarn translate i get the following error:

yarn run v1.22.19
$ wp-pot --src '**/**/**/*.php' --dest-file 'languages/test-plugin.pot' --package 'test-plugin' --domain 'test-plugin' --last-translator 'Test Plugin <[email protected]>' --team 'Test Plugin <[email protected]>' --bug-report 'testplugin.com'
The system cannot find the file specified.
error Command failed with exit code 1.

To Reproduce
run yarn translate (wp-pot)

This will throw the following error:
The system cannot find the file specified.
error Command failed with exit code 1.

Module versions
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]

Additional context
What can cause this issue, can't find anything related to it.

Without email (<[email protected]> for example) in --teams & --last-translator options it works :
translate": "wp-pot --src '**/**/**/*.php' --dest-file 'languages/test-plugin.pot' --package 'test-plugin' --domain 'test-plugin' --bug-report 'testplugin.com' --team 'Test Plugin' --last-translator 'Test Plugin'"

An in-range update of eslint-config-standard is breaking the build 🚨

The devDependency eslint-config-standard was updated from `14.0.1` to `14.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ node-multi-build: * node-v11 - Failed

node-latest - Failed
node-v8 - Failed
node-v10 - Failed

Commits

The new version differs by 3 commits.

d1dacfc 14.1.0
adba47f BREAKING: eslint@>=6.2.2
6b22f77 ecmaVersion: 2020

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-node is breaking the build 🚨

Version 7.0.1 of eslint-plugin-node was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-node
Current Version	7.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v7.0.1

Bug fixes

It fixed false positive that the node/no-unsupported-features/node-builtins reports the process.emitWarning method on Node.js >=6 <8. It was supported since Node.js 6.0.0.

Commits

The new version differs by 3 commits.

a4a7ad2 7.0.1
44b57ed Fix: false positive 'no-unsupported-features/node-builtins'
cde4c82 Docs: update README.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from `5.15.3` to `5.16.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ node-multi-build: * node-v11 - Failed

node-v8 - Failed
node-latest - Failed
node-v10 - Failed

Release Notes for v5.16.0

dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)

Commits

The new version differs by 11 commits.

ded2f94 5.16.0
ea36e13 Build: changelog update for 5.16.0
dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
b452f27 Chore: Update README to pull in reviewer data (#11506)
afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
4fe7eb7 Chore: use nyc instead of istanbul (#11532)
f16af43 Chore: fix formatters/table test (#11534)
78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from `5.12.1` to `5.13.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v5.13.0

91c8884 Chore: use local function to append "s" instead of a package (#11293) (Timo Tijhof)
b5143bf Update: for-direction detection false positives/negatives (#11254) (Ruben Bridgewater)
9005e63 Chore: increase camelcase test coverage (#11299) (Redmond Tran)
5b14ad1 Fix: false positive in no-constant-condition (fixes #11306) (#11308) (Pig Fang)
6567c4f Fix: only remove arrow before body in object-shorthand (fixes #11305) (#11307) (Pig Fang)
fa2f370 Docs: update rule configuration values in examples (#11323) (Kai Cataldo)
0a3c3ff New: Allow globals to be disabled/configured with strings (fixes #9940) (#11338) (Teddy Katz)
dccee63 Chore: avoid hard-coding the list of core rules in eslint:recommended (#11336) (Teddy Katz)
c1fd6f5 Chore: remove undocumented Linter#rules property (refs #9161) (#11335) (Teddy Katz)
36e3356 Chore: remove dead code for loading rules (#11334) (Teddy Katz)
c464e27 Docs: Rename result -> foo (#11210) (Alexis Tyler)

Commits

The new version differs by 13 commits.

4b267a5 5.13.0
720dce1 Build: changelog update for 5.13.0
91c8884 Chore: use local function to append "s" instead of a package (#11293)
b5143bf Update: for-direction detection false positives/negatives (#11254)
9005e63 Chore: increase camelcase test coverage (#11299)
5b14ad1 Fix: false positive in no-constant-condition (fixes #11306) (#11308)
6567c4f Fix: only remove arrow before body in object-shorthand (fixes #11305) (#11307)
fa2f370 Docs: update rule configuration values in examples (#11323)
0a3c3ff New: Allow globals to be disabled/configured with strings (fixes #9940) (#11338)
dccee63 Chore: avoid hard-coding the list of core rules in eslint:recommended (#11336)
c1fd6f5 Chore: remove undocumented Linter#rules property (refs #9161) (#11335)
36e3356 Chore: remove dead code for loading rules (#11334)
c464e27 Docs: Rename result -> foo (#11210)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Exclude directory

Let's say I want to exclude a specific directory: I've tried with an array like this --src ['**/*.php', '!dist/**/*.php'] as suggested on wp-pot docs but no success. Any advice?

An in-range update of wp-pot is breaking the build 🚨

Version 1.6.3 of wp-pot was just published.

Branch	Build failing 🚨
Dependency	wp-pot
Current Version	1.6.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

wp-pot is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes

v1.6.3

Update php-parser to version 3.0.0-prerelease.3

Commits

The new version differs by 5 commits.

50a6630 1.6.3
6991b9b Merge pull request #51 from rasmusbe/greenkeeper/php-parser-3.0.0-prerelease.3
6a6fc4f update lockfile
2dbe484 fix(package): update php-parser to version 3.0.0-prerelease.3
19b27b2 fix travis and greenkeeper

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Dependency Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

chore(deps): update dependency minimist to 1.2.6 [security]
chore(deps): update dependency mocha to v9.2.2
chore(deps): update actions/cache action to v3
chore(deps): update actions/checkout action to v3
Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

chore(deps): update node.js to v16

Check this box to trigger a request for Renovate to run again on this repository

An in-range update of eslint-plugin-promise is breaking the build 🚨

Version 4.0.1 of eslint-plugin-promise was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-promise
Current Version	4.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-promise is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 3 commits.

61a373c 4.0.1
1b01507 docs(changelog): prepare for v4.0.1
af28d6f fix(param-names): remove fixer (#146)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 10 commits.

44ca158 update utils changelog
a3728d7 bump eslint-module-utils to v2.1.0
3e29169 bump v2.4.0
ea9c92c Merge pull request #737 from kevin940726/master
8f9b403 fix typos, enforce type of array of strings in allow option
95315e0 update CHANGELOG.md
28e1623 eslint-module-utils: filePath in parserOptions (#840)
2f690b4 update CI to build on Node 6+7 (#846)
7d41745 write doc, add two more tests
dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Scan subfolders?

It doesn't seem like the command scans through subfolders, just the top level folder and then creates the translations for the files in that top level folder

wp-pot / wp-pot-cli Goto Github PK

wp-pot-cli's Introduction

Like my work and want to say thanks?

Install

Usage

Related

License

wp-pot-cli's People

Contributors

Stargazers

Watchers

Forkers

wp-pot-cli's Issues

The dependency wp-pot was updated from 1.6.3 to 1.6.4.

Version 1.6.2 of wp-pot was just published.

Version 1.3.0 of wp-pot just got published.

The devDependency eslint-config-standard was updated from 14.0.1 to 14.1.0.

Version 7.0.1 of eslint-plugin-node was just published.

Bug fixes

The devDependency eslint was updated from 5.15.3 to 5.16.0.

The devDependency eslint was updated from 5.12.1 to 5.13.0.

Version 1.6.3 of wp-pot was just published.

Open

Ignored or Blocked

Version 4.0.1 of eslint-plugin-promise was just published.

Version 2.4.0 of eslint-plugin-import just got published.

Recommend Projects

Recommend Topics

Recommend Org

The dependency wp-pot was updated from `1.6.3` to `1.6.4`.

The devDependency eslint-config-standard was updated from `14.0.1` to `14.1.0`.

The devDependency eslint was updated from `5.15.3` to `5.16.0`.

The devDependency eslint was updated from `5.12.1` to `5.13.0`.