feat(demo): add new CLI demo covering all supported file formats#2114
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughA new Changesnew-cli Demo Project
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Adds a runnable demo for the new
@lingo.dev/cliunderdemo/new-cli/, alongside the existing compiler demos.What's inside
.lingo/config.jsonwith onefiles[]entry per supported format (no org/engine binding, so users runlingo linkto connect their own).content/en/sources covering every format: JSON, JSONC, Markdown, MDX, Markdoc, OpenAPI YAML, each exercising a format-specific option (lockedKeys, preservedKeys, translateFrontmatterFields, translateComponentProps).content/de|fr|es/sample output plus.lingo/lock.json, matching the old CLI demo pattern (committed translations).README.md: get viadegit, thenlogin->link->push --estimate(preview cost) ->push->pull.Verified
Ran the full flow end to end against a real engine on
@lingo.dev/cli@1.7.0: push submitted the async run, pull wrote 18 target files, translations are real (lockedKeys honored), andpush --estimatereturns a per-locale cost breakdown.No changeset:
@lingo.dev/demo-new-cliis private, nothing published.Summary by CodeRabbit
New Features
Documentation