fix: remove demo conditional restrictions & update the creation process

[irisSong]

🤔 这个变动的性质是？

• 新特性提交
• 日常 bug 修复
• 站点、文档改进
• 演示代码改进
• 组件样式/交互改进
• TypeScript 定义更新
• 包体积优化
• 性能优化
• 功能增强
• 国际化改进
• 重构
• 代码风格优化
• 测试用例
• 分支合并
• 其他改动（是关于什么的改动？）

🔗 相关 Issue

💡 需求背景和解决方案

☑️ 请求合并前的自查清单

⚠️ 请自检并全部勾选全部选项。⚠️

• 文档已补充或无须补充
• 代码演示已提供或无须提供
• TypeScript 定义已补充或无须补充
• fork仓库代码是否为最新避免文件冲突
• Files changed 没有 package.json lock 等无关文件

Summary by CodeRabbit

本次更新针对构建流程和组件展示进行了优化和重构，为您提供更一致直观的体验：

• Chores
  • 更新构建命令命名，确保流程一致性。
• New Features
  • 优化组件示例展示，支持动态渲染实际组件，提升展示直观性。
• Refactor
  • 调整组件默认配置和页面入口设置，简化生成流程，提高构建效率。

[coderabbitai]

Walkthrough

此次更改主要集中在脚本和组件逻辑上。在根目录的 package.json 中，将构建脚本从 build:jstaro:site:jmapp 重命名为 build:jdtaro:site:jmapp，保持命令一致。其它改动包括：调整组件创建时 newCpt 对象的默认值、修改 demo 模块的类型声明与动态渲染逻辑、移除用于更新页面入口文件的 updatePages 函数以及清理 Taro 页面生成中的适配逻辑。

Changes

文件	更改摘要
package.json	重命名脚本：替换 build:jstaro:site:jmapp 为 build:jdtaro:site:jmapp，命令保持一致
scripts/create-component-mode.js	更新 newCpt 对象：将 dd 属性从 true 改为 false
scripts/demo.js	修改 demoModel 函数：更新类型声明和动态组件渲染逻辑
scripts/.../update-taro-entry.js	移除 updatePages 函数及其相关文件写入操作
scripts/.../generate-taro-pages.js	清理组件适配逻辑：移除条件判断，统一赋值 demoContent

Sequence Diagram(s)

sequenceDiagram
    participant U as 用户
    participant S as 构建脚本
    participant C as checked:taro
    participant G as generate:file:taro:pages
    participant B as nutui-taro-demo build
    U->>S: 执行 "build:jdtaro:site:jmapp"
    S->>C: 运行 checked:taro 脚本
    C-->>S: 完成检查
    S->>G: 运行 generate:file:taro:pages 脚本
    G-->>S: 页面生成完成
    S->>B: 调用 nutui-taro-demo build:h5
    B-->>S: 构建完成
    S-->>U: 返回结果

Loading

Possibly related PRs

• chore: support pnpm workspace #2842: 更新 package.json 中构建脚本，增加了 build:jdtaro:site，与此次脚本重命名改动相关联。

Suggested reviewers

• xiaoyatong
• oasis-cloud

Poem

代码变更迎春风，
脚本更新步步通。
组件逻辑添新彩，
功能如兔轻快奔。
新旧交替谱乐章，
程序世界更辉煌！
🐰✨

---

📜 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 d07e815 and 24efb9f.

📒 Files selected for processing (5)

• package.json (1 hunks)
• scripts/create-component-mode.js (1 hunks)
• scripts/demo.js (4 hunks)
• scripts/harmony/update-taro-entry.js (1 hunks)
• scripts/taro/generate-taro-pages.js (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build
• GitHub Check: test

🔇 Additional comments (4)

scripts/harmony/update-taro-entry.js (1)

11-11: 代码格式优化

在 if 条件语句后添加了空格，提高了代码的可读性和一致性。

scripts/taro/generate-taro-pages.js (1)

43-44: 简化了演示内容生成逻辑

移除了条件判断逻辑，使演示内容的生成更加直接和清晰。这种改进有助于减少代码复杂性。

scripts/demo.js (1)

115-115: 改进了组件类型定义和渲染逻辑

1. 使用了更具体的组件类型 ${name}Props，提高了类型安全性
2. 组件渲染现在使用动态组件名称，增加了灵活性

这些改进使组件更加通用和可维护。

Also applies to: 124-124, 144-144, 153-153

scripts/create-component-mode.js (1)

19-19:

❓ Verification inconclusive

验证组件创建的默认行为变更

将 dd 属性的默认值从 true 改为 false 可能会影响组件的创建过程。请确认：

1. 这个改动是否会影响现有组件的构建流程
2. 是否需要更新相关文档来反映这个变更

---

🏁 Script executed:

#!/bin/bash
# 检查是否有其他文件依赖 dd 属性的默认值
rg "dd.*true" --type js --type ts

Length of output: 1714

---

关于 dd 默认值变更的验证

在 scripts/create-component-mode.js 中，将 dd 属性的默认值从 true 改为了 false。现阶段我们通过代码检索没有发现其他文件直接依赖该默认值，但鉴于此修改可能对组件的创建逻辑产生影响，请注意以下事项：

• 请确认组件创建及构建流程是否依赖 dd 属性的默认值；
• 如有必要，请同步更新相关文档，确保变更对现有组件行为的影响被正确说明和管理。

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.75%. Comparing base (ec4c186) to head (24efb9f).
Report is 8 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #2991   +/-   ##
==========================================
  Coverage      85.75%   85.75%           
==========================================
  Files            277      277           
  Lines          18110    18110           
  Branches        2735     2735           
==========================================
  Hits           15531    15531           
  Misses          2574     2574           
  Partials           5        5           

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