Skip to content

chore(l10n): migrate CLI to yargs#1378

Open
LeoMcA wants to merge 1 commit intomainfrom
l10n-yargs
Open

chore(l10n): migrate CLI to yargs#1378
LeoMcA wants to merge 1 commit intomainfrom
l10n-yargs

Conversation

@LeoMcA
Copy link
Copy Markdown
Member

@LeoMcA LeoMcA commented Mar 13, 2026

Migrates the l10n cli to use yargs, and moves the current base command into an extract command.

This will make it easier to add future commands in the (near) future (e.g. npm l10n merge)

@LeoMcA LeoMcA requested review from a team and mdn-bot as code owners March 13, 2026 12:23
@LeoMcA LeoMcA requested a review from caugner March 13, 2026 12:23
@github-actions
Copy link
Copy Markdown
Contributor

2a5892a was deployed to: https://fred-pr1378.review.mdn.allizom.net/

Comment thread l10n/cli.js
"Generates template.ftl by combining en-US.ftl and inline l10n tagged strings",
builder: (yargs) =>
yargs
.option("lint", {
Copy link
Copy Markdown
Contributor

@caugner caugner Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be a separate lint command?

Otherwise, to avoid confusion, we could call the option check (like prettier --check and cargo fmt -- --check).

Comment thread l10n/cli.js
}
await yargs(hideBin(process.argv))
.command({
command: "extract",
Copy link
Copy Markdown
Contributor

@caugner caugner Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be called sync or fix?

@caugner caugner changed the title chore: migrate l10n cli to yargs chore(l10n): migrate CLI to yargs Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants