Revert "fix: merge mako config"

[stormslowly]

Reverts #1578

Summary by CodeRabbit

• 新功能
  • 修改了配置检索的行为，确保返回的配置不再包含潜在的合并属性。

[coderabbitai]

Walkthrough

此次更改主要涉及 packages/bundler-mako/index.js 文件中的 getMakoConfig 函数。修改的核心内容是移除了将 mako 对象合并到 makoConfig 对象中的逻辑。现在，该函数仅返回 makoConfig，这意味着之前在合并过程中包含的 mako 对象的属性将不再出现在最终返回的配置中。这一变化可能会影响配置的构建和后续的使用方式。

Changes

文件路径	更改摘要
packages/bundler-mako/index.js	移除了 getMakoConfig 函数中将 mako 合并到 makoConfig 的逻辑，现仅返回 makoConfig。

Possibly related PRs

• fix: merge mako config #1578: 此PR直接修改了同一文件中的 getMakoConfig 函数，改变了返回行为以合并配置，与主PR讨论的配置处理相关。

Poem

🐇 在草地上跳跃，欢声笑语，
配置简化，清晰如初。
不再合并，轻松自在，
兔子欢呼，乐在其中！
让代码更明了，未来更辉煌！ 🌟

Tip

OpenAI O1 model for chat

• We have deployed OpenAI's latest O1 model for chat.
• OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
• Please share any feedback with us in the discussions post.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7e89e0e and 0509173.

Files selected for processing (1)

• packages/bundler-mako/index.js (1 hunks)

Additional comments not posted (1)

packages/bundler-mako/index.js (1)

680-680: 潜在的重大变更：配置检索行为已更改

此更改通过不将 mako 对象中的属性包含在最终的 makoConfig 中来改变配置检索的行为。这可能会破坏依赖于 mako 对象中的属性出现在最终配置中的代码。

请运行以下脚本来验证删除 mako 的合并不会在代码库中引起任何问题：

Verification successful

---

验证成功：移除 mako 对象的合并不会引起问题

经过验证，代码库中没有直接或间接依赖于 mako 对象的属性的情况。因此，移除 mako 对象的合并不会对现有功能造成影响。

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 描述：验证代码库中对 `makoConfig` 的使用不依赖于 `mako` 对象中的属性

# 测试：搜索 `makoConfig` 的使用情况，检查是否有任何代码直接访问来自 `mako` 的属性
# 预期结果：没有代码直接访问 `makoConfig.mako` 或 `makoConfig.mako.someProperty` 
rg --type js -A 5 $'makoConfig\\.(mako|mako\\.\\w+)'

Length of output: 50

---

Script:

#!/bin/bash
# 描述：进一步验证代码库中对 `makoConfig` 的使用是否间接依赖于 `mako` 对象中的属性

# 测试：搜索 `makoConfig` 的使用情况，检查是否有任何代码通过其他方式依赖于 `mako` 对象
# 预期结果：没有代码通过其他方式依赖于 `mako` 对象中的属性
rg --type js -A 10 'makoConfig' | grep -i 'mako'

Length of output: 5982

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.17%. Comparing base (7e89e0e) to head (0509173).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1589   +/-   ##
=======================================
  Coverage   62.17%   62.17%           
=======================================
  Files         128      128           
  Lines       15528    15528           
=======================================
  Hits         9655     9655           
  Misses       5873     5873           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.