fix: await lexer init

[joshunrau]

• add --verbose option for build
• improve error message if validation schema is not defined for route

Summary by CodeRabbit

• New Features

  • Introduced a new CLI flag (‑‑verbose) for the build process, allowing users to enable detailed logging and receive enhanced execution feedback during builds.

• Bug Fixes

  • Improved error messaging for schema validations, providing clearer guidance on proper schema configuration to help troubleshoot validation issues more effectively.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates several parts of the system to improve asynchronous handling and logging. In the CLI tests and command, the callback invocation is now awaited with a defined context, and a new --verbose option has been introduced. The build process has been restructured by integrating the former bundle functionality into the buildProd function with enhanced verbose logging. Additionally, test suites have been consolidated and updated, and error messages in the validation logic have been refined for both schema tests and utilities.

Changes

File(s)	Change Summary
src/cli/.../libnest-build.test.ts, src/cli/libnest-build.js	Updated async callback invocation in tests; added new CLI option --verbose with buildProd accepting an extra verbose parameter.
src/meta/.../build.test.ts, src/meta/build.ts	Consolidated bundle testing into buildProd tests; restructured buildProd to nest the previous bundle function with enhanced verbose logging and updated configuration (mode change from 'module' to 'server').
src/meta/parse.ts	Added asynchronous initialization with await lexer.init to ensure proper setup before parsing entry functions.
src/pipes/.../validation.pipe.test.ts, src/utils/validation.utils.ts	Updated error messages and test cases for schema validation errors: specifies errors when schemas are undefined on a class or plain object, while providing clearer guidance on using Body() and proper class importing.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant CLI
  participant BuildProd
  participant Bundle
  
  User->>CLI: Run command with --verbose option
  CLI->>BuildProd: Invoke buildProd({ configFile, verbose: true })
  BuildProd->>Bundle: Execute nested bundle function with verbose logging
  Bundle-->>BuildProd: Return bundling result
  BuildProd-->>CLI: Send build status/result

Loading

sequenceDiagram
  participant Caller
  participant Lexer
  participant Parser
  
  Caller->>Lexer: Await lexer initialization (await lexer.init)
  Lexer-->>Caller: Initialization complete
  Caller->>Parser: Invoke parseEntryFromFunction
  Parser-->>Caller: Return parsed entry

Loading

Possibly related PRs

• fix: await lexer init #30: The changes in the main PR and the retrieved PR are related as both involve modifications to the buildProd function, specifically the addition of a verbose parameter and its handling in the test cases.

Poem

I’m hopping through the lines of code,
With async treats and logs that glow,
Verbose whispers in each function call,
Tests are dancing, standing tall,
A bunny cheers—let improvements show! 🥕🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3275d88 and f80b710.

📒 Files selected for processing (7)

• src/cli/__tests__/libnest-build.test.ts (1 hunks)
• src/cli/libnest-build.js (1 hunks)
• src/meta/__tests__/build.test.ts (4 hunks)
• src/meta/build.ts (2 hunks)
• src/meta/parse.ts (1 hunks)
• src/pipes/__tests__/validation.pipe.test.ts (1 hunks)
• src/utils/validation.utils.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

🎉 This PR is included in version 4.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀