chore(test): refactor build-system test

[Sma1lboy]

Summary by CodeRabbit

Based on the comprehensive summary of changes, here are the release notes:

Release Notes

• Test Improvements

  • Enhanced test suite for build system handlers
  • Streamlined test execution and logging processes
  • Removed deprecated test files and consolidated testing approaches

• Build System Enhancements

  • Introduced new utility functions for code generation and processing
  • Updated handler interactions with language models
  • Improved response formatting and error handling
  • Added new interfaces and type definitions

• Model Interaction Changes

  • Refined chat model interaction structure
  • Updated message role definitions
  • Standardized prompt and response handling

• Embedding and Server Modifications

  • Simplified embedding request handling
  • Improved logging and error reporting in embedding providers

• Code Quality

  • Removed deprecated utility functions
  • Enhanced code readability and formatting
  • Consolidated response processing methods

[coderabbitai]

Caution

Review failed

The pull request is closed.

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

backend/src/build-system/__tests__/test-generate-doc.spec.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-prettier".

(The package "eslint-plugin-prettier" was not found when loaded as a Node module from the directory "/backend".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-prettier@latest --save-dev

The plugin "eslint-plugin-prettier" was referenced from the config file in "backend/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

This pull request introduces comprehensive modifications across multiple files in the backend build system, focusing on standardizing model interaction, response handling, and build sequence execution. The changes primarily involve updating how chat models are invoked, processing model responses, and refining utility functions for string manipulation and JSON extraction. A new handler for Level 2 UX Sitemap Structure has been added, and several existing handlers have been updated to use consistent methods for generating and processing content.

Changes

File Path	Change Summary
backend/src/build-system/__tests__/utils.ts	Added objectToMarkdown, executeBuildSequence, and TestResult interface
backend/src/build-system/handlers/*/	Updated model interaction to use structured messages with roles
backend/src/build-system/utils/strings.ts	Added utility functions: parseGenerateTag, removeCodeBlockFences, formatResponse, extractJsonFromText
backend/src/build-system/types.ts	Added FileStructOutput interface
backend/src/chat/message.model.ts	Updated MessageRole enum

Sequence Diagram

sequenceDiagram
    participant Context as BuilderContext
    participant Handler as BuildHandler
    participant ModelProvider as ModelProvider
    participant Utilities as StringUtilities

    Context->>Handler: run()
    Handler->>ModelProvider: chatSync(messages)
    ModelProvider-->>Handler: model response
    Handler->>Utilities: formatResponse(response)
    Utilities-->>Handler: processed content
    Handler->>Context: return BuildResult

Loading

Possibly related PRs

• Feat(backend) file structure #59: File structure document generation
• Feat(bcakend) more detail ux structure #62: UX sitemap structure document generation
• Feat(backend)file generate function specific place #71: Path utility test suite
• Chang file arch input variable name to datamapDoc avoid misleading #77: Data mapping variable renaming

Suggested reviewers

• ZHallen122

Poem

🐰 Code hops and leaps with grace,
Handlers dance, a rhythmic pace
Strings untangled, models bright
Build system shines with pure delight!
Refactored magic, clean and neat 🌟

---

📜 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 f9b0ed5 and 757ab4f.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (27)

• backend/src/build-system/__tests__/test-database-schemas.spec.ts (0 hunks)
• backend/src/build-system/__tests__/test-generate-doc.spec.ts (2 hunks)
• backend/src/build-system/__tests__/test.fullstack-gen.spec.ts (7 hunks)
• backend/src/build-system/__tests__/test.model-provider.spec.ts (1 hunks)
• backend/src/build-system/__tests__/utils.ts (2 hunks)
• backend/src/build-system/handlers/backend/code-generate/index.ts (2 hunks)
• backend/src/build-system/handlers/backend/file-review/file-review.ts (4 hunks)
• backend/src/build-system/handlers/backend/requirements-document/index.ts (3 hunks)
• backend/src/build-system/handlers/database/requirements-document/index.ts (2 hunks)
• backend/src/build-system/handlers/database/schemas/schemas.ts (4 hunks)
• backend/src/build-system/handlers/file-manager/file-arch/index.ts (5 hunks)
• backend/src/build-system/handlers/file-manager/file-arch/prompt.ts (3 hunks)
• backend/src/build-system/handlers/file-manager/file-structure/index.ts (5 hunks)
• backend/src/build-system/handlers/product-manager/product-requirements-document/prd.ts (2 hunks)
• backend/src/build-system/handlers/ux/datamap/index.ts (2 hunks)
• backend/src/build-system/handlers/ux/sitemap-document/uxsmd.ts (2 hunks)
• backend/src/build-system/handlers/ux/sitemap-structure/index.ts (2 hunks)
• backend/src/build-system/handlers/ux/sitemap-structure/sms-page.ts (1 hunks)
• backend/src/build-system/hanlder-manager.ts (2 hunks)
• backend/src/build-system/types.ts (1 hunks)
• backend/src/build-system/utils/database-utils.ts (0 hunks)
• backend/src/build-system/utils/strings.ts (2 hunks)
• backend/src/chat/message.model.ts (1 hunks)
• backend/src/common/model-provider/index.ts (1 hunks)
• backend/src/common/model-provider/types.ts (1 hunks)
• llm-server/src/embedding/openai-embedding-provider.ts (4 hunks)
• llm-server/src/main.ts (2 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.