Skip to content

docs: add logs command reference and backend function best practices#112

Draft
yoavf wants to merge 2 commits into
mainfrom
docs/cli-logs-and-backend-best-practices
Draft

docs: add logs command reference and backend function best practices#112
yoavf wants to merge 2 commits into
mainfrom
docs/cli-logs-and-backend-best-practices

Conversation

@yoavf
Copy link
Copy Markdown

@yoavf yoavf commented Mar 28, 2026

Summary

  • Added logs command reference to CLI skill (correct syntax with --function flag)
  • Added "Backend Function Best Practices" section to SDK skill covering:
    • Avoid scanning large collections with list()
    • Use filter() with specific conditions
    • Use pagination with skip
    • Use REST API for data migrations
  • Fixed pre-existing bug: wrong log level values in troubleshooter docs (log and warn changed to warning)
  • Added cross-reference to base44-troubleshooter for detailed logs docs

Motivation

During b44emoji development, we used bare npx base44 logs and got interleaved output from all functions, not realizing --function filtering existed. We also hit response size limits in Deno backend functions and had to redesign from scratch. These docs would have saved significant time.

Test plan

  • Verify logs command flags match actual CLI implementation
  • Verify log level values match LogLevelSchema in CLI source
  • Check REST API inline URL is correct
  • Verify troubleshooter cross-reference is accurate

🤖 Generated with Claude Code

yoavf and others added 2 commits March 28, 2026 23:36
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

1 participant