Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: 适配效能插件的fix #17514

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

zhengyanan1
Copy link
Contributor

@zhengyanan1 zhengyanan1 commented Apr 11, 2025

这个 PR 做了什么? (简要描述所做更改)
command为空时(Taro项目外的taro命令,去掉所有build阶段加载的全局插件)

这个 PR 是什么类型? (至少选择一个)

  • 错误修复(Bugfix) issue: fix #
  • 新功能(Feature)
  • 代码重构(Refactor)
  • TypeScript 类型定义修改(Typings)
  • 文档修改(Docs)
  • 代码风格更新(Code style update)
  • 其他,请描述(Other, please describe):

这个 PR 涉及以下平台:

  • 所有小程序
  • 微信小程序
  • 支付宝小程序
  • 百度小程序
  • 字节跳动小程序
  • QQ 轻应用
  • 京东小程序
  • 快应用平台(QuickApp)
  • Web 平台(H5)
  • 移动端(React-Native)
  • 鸿蒙(harmony)

Summary by CodeRabbit

  • 新功能
    • 当未提供特定参数时,系统将自动剔除不相关的插件,从而优化全局配置的处理逻辑。

Copy link

coderabbitai bot commented Apr 11, 2025

Walkthrough

packages/taro-service/src/utils/index.ts 中新增了常量 ExcludePluginTagsForNullCommand,用于存储在 filterGlobalConfig 函数中需要排除的插件标签。当传入的 command 参数为假值时,函数会检查 config.plugins 数组,并移除其中包含这些标签的插件,然后返回更新后的配置;当 command 为真时,沿用原有基于 RelatedPluginTag 的过滤逻辑。

Changes

文件 变更描述
packages/taro-service/src/.../index.ts 新增 ExcludePluginTagsForNullCommand 常量,修改 filterGlobalConfig 函数:在 command 为假时过滤 config.plugins 数组中的插件

Sequence Diagram(s)

sequenceDiagram
    participant C as Caller
    participant F as filterGlobalConfig
    participant P as Plugins
    
    C->>F: 调用 filterGlobalConfig(globalConfig, command)
    alt command 为假(null/falsy)
        F->>P: 检查并过滤包含 ExcludePluginTagsForNullCommand 的插件
        F-->>C: 返回更新后的 config
    else command 为真
        F->>P: 根据 RelatedPluginTag 执行插件过滤
        F-->>C: 返回处理后的 config
    end
Loading

Possibly related PRs

Suggested reviewers

  • tutuxxx

Poem

萌兔跳跃在代码间,
新增常量闪耀似星🌟。
命令真假分明有序,
过滤插件显神奇。
代码世界乐无边,
我在这里蹦跶欢欣!
🐰 编程梦想共飞扬!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.

@coderabbitai coderabbitai bot requested a review from tutuxxx April 11, 2025 05:59
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/taro-service/src/utils/index.ts (1)

123-131: 优化命令为空时的配置过滤逻辑

当命令为空时,现在会过滤掉包含特定标签的插件,而不是直接返回原始配置。这解决了PR中提到的问题,防止在命令为空时加载不必要的插件。

建议使用可选链操作符来避免潜在的空值错误:

-  if (config.plugins?.length) {
+  if (config.plugins?.length) {
   config.plugins = config.plugins.filter(pluginName => {
     return !ExcludePluginTagsForNullCommand.some(tag => pluginName.includes(tag))
   })
 }

另外,考虑添加类型检查以确保 pluginName 是字符串类型:

 config.plugins = config.plugins.filter(pluginName => {
-  return !ExcludePluginTagsForNullCommand.some(tag => pluginName.includes(tag))
+  return typeof pluginName === 'string' && !ExcludePluginTagsForNullCommand.some(tag => pluginName.includes(tag))
 })
🧰 Tools
🪛 Biome (1.9.4)

[error] 127-127: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5b53c7c and be7bea7.

📒 Files selected for processing (1)
  • packages/taro-service/src/utils/index.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/taro-service/src/utils/index.ts (1)
packages/taro/types/compile/config/project.d.ts (1)
  • IProjectConfig (210-323)
🪛 Biome (1.9.4)
packages/taro-service/src/utils/index.ts

[error] 127-127: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Build Rust Binding / stable - aarch64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
🔇 Additional comments (1)
packages/taro-service/src/utils/index.ts (1)

121-121: 新增常量用于排除特定插件标签

这个常量定义了当命令为空时需要排除的插件标签列表。目前只包含一个标签 @jdtaro/plugin-build-。这是一个良好的实践,将这些标签统一管理,便于未来扩展。

Copy link

codecov bot commented Apr 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.70%. Comparing base (5b53c7c) to head (be7bea7).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff            @@
##             main   #17514    +/-   ##
========================================
  Coverage   57.70%   57.70%            
========================================
  Files         469      469            
  Lines       26551    26551            
  Branches     5859     5842    -17     
========================================
  Hits        15321    15321            
- Misses       9608     9727   +119     
+ Partials     1622     1503   -119     
Flag Coverage Δ
taro-cli 72.37% <ø> (ø)
taro-runtime 59.87% <ø> (ø)
taro-web 49.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 25 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Single-Dancer Single-Dancer added this to the 4.0.11 milestone Apr 11, 2025
This was referenced Apr 12, 2025
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.

2 participants