feat: del blockToWebComponentTemplate
English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:
- [x] The commit message follows our Commit Message Guidelines
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
- [ ] Built its own designer, fully self-validated
PR Type
What kind of change does this PR introduce?
- [ ] Bugfix
- [x] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Documentation content changes
- [ ] Other... Please describe:
Background and solution
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
- [x] Yes
- [ ] No
Other information
Summary by CodeRabbit
- Chores
- Removed the entire block-to-web-component template package, including all related files and documentation. This package is no longer available in the project.
Walkthrough
The changes involve the complete removal of the @opentiny/tiny-engine-blockToWebComponentTemplate package. All core files, including the Vue component, library entry, build configuration, README documentation, and package metadata, have been deleted. This eliminates the package's ability to convert blocks into web components, as well as all related build scripts, dependencies, and usage instructions. No exported entities or configurations remain from this package. Additionally, documentation was updated to add deprecation warnings for older block release and LAN release solutions and to clarify backend support for the new block construction scheme starting TinyEngine version 2.1.
Changes
| File(s) | Change Summary |
|---|---|
| packages/blockToWebComponentTemplate/README.md | Deleted the README file containing package purpose and usage instructions. |
| packages/blockToWebComponentTemplate/package.json | Deleted the package metadata, dependencies, scripts, and configuration. |
| packages/blockToWebComponentTemplate/src/BlockFileName.vue | Deleted the main Vue component responsible for block-to-web-component conversion UI. |
| packages/blockToWebComponentTemplate/src/lib.js | Deleted the library entry file that registered and exported the web component as a custom element. |
| packages/blockToWebComponentTemplate/vite.config.js | Deleted the Vite build configuration for compiling the package into web components. |
| docs/solutions/block-construction-solution.md | Added backend support info for new block construction scheme starting TinyEngine v2.1. |
| docs/solutions/block-lan-release-solution.md | Added deprecation warning advising to use new block construction solution from TinyEngine v2.1. |
| docs/solutions/block-release-solution.md | Added deprecation warning advising to use new block construction solution from TinyEngine v2.1. |
Poem
The block-to-web dream has hopped away,
No more templates in Vue to display.
Scripts and configs, all swept from sight,
The bunny waves goodbye, bounding light.
With empty folders and code now gone,
The garden waits for a brand new dawn.
🐇✨
📜 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 4edb74e396a5ea1b985a7af51c40028b3435cd10 and 68f15dd0c963b6f1a26ec44c7cdc32774d8fd2f9.
📒 Files selected for processing (8)
docs/solutions/block-construction-solution.md(2 hunks)docs/solutions/block-lan-release-solution.md(1 hunks)docs/solutions/block-release-solution.md(1 hunks)packages/blockToWebComponentTemplate/README.md(0 hunks)packages/blockToWebComponentTemplate/package.json(0 hunks)packages/blockToWebComponentTemplate/src/BlockFileName.vue(0 hunks)packages/blockToWebComponentTemplate/src/lib.js(0 hunks)packages/blockToWebComponentTemplate/vite.config.js(0 hunks)
💤 Files with no reviewable changes (5)
- packages/blockToWebComponentTemplate/README.md
- packages/blockToWebComponentTemplate/src/lib.js
- packages/blockToWebComponentTemplate/src/BlockFileName.vue
- packages/blockToWebComponentTemplate/vite.config.js
- packages/blockToWebComponentTemplate/package.json
🚧 Files skipped from review as they are similar to previous changes (3)
- docs/solutions/block-release-solution.md
- docs/solutions/block-lan-release-solution.md
- docs/solutions/block-construction-solution.md
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: push-check
✨ 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.
🪧 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.Explain this complex logic.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:@coderabbitai explain this code block.@coderabbitai modularize this function.
- PR comments: Tag
@coderabbitaiin 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 explain its main purpose.@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.
Support
Need help? Create a ticket on our support page for assistance with any issues or questions.
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 pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai generate docstringsto generate docstrings for this PR.@coderabbitai generate sequence diagramto generate a sequence diagram of the changes in this PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.