fix(scripts): add missing target flag for llms-txt generator - #261
fix(scripts): add missing target flag for llms-txt generator#261sameerchore wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe Merge Risk: ⚪ Minimal · up to The HTML documentation build now also generates the Orama database target alongside existing outputs. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
could you rebase :) |
Signed-off-by: Sameer Chore <sameerchore5@gmail.com>
91ef123 to
b646bae
Compare
Summary
In
scripts/html/index.mjs, theweb,orama-db, andsitemaptargets use the-tflag explicitly.llms-txtwas missing its own-tflag. This change adds it for consistency:The CLI was handling
llms-txtcorrectly, But by this change it just makes the arguments consistent and easier to maintain for future target additions .What kind of change does this PR introduce?
Did you add tests for your changes?
No new tests were added because this is a small CLI argument formatting change.
The following checks were run successfully:
npm run lintnpm run format:checknpm testcoderabbit review --agent— 0 findingsDoes this PR introduce a breaking change?
No.
Documentation
No documentation changes are needed because this is an internal build script change.
Use of AI
AI was used to understand behaviour of inconsistent flag in
scripts/html/index.mjsonly.Summary by CodeRabbit
orama-dbtarget.