Ospp 2024/feat schema render #780
Conversation
…timizing code formatting
…tiny/tiny-engine into ospp-2024/004-ai-multimodal
WalkthroughThe changes in this pull request involve updates to several components of the AI chat interface, enhancing user interaction and functionality. The Changes
Possibly related PRs
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- packages/plugins/robot/src/ContentDialog.vue (1 hunks)
- packages/plugins/robot/src/Main.vue (1 hunks)
- packages/plugins/robot/src/js/useDialogContent.js (2 hunks)
Additional context used
GitHub Check: push-check
packages/plugins/robot/src/Main.vue
[failure] 283-283:
Unexpected console statement
Additional comments not posted (7)
packages/plugins/robot/src/ContentDialog.vue (3)
48-52: LGTM!The code changes are approved. The hover effect for the code block has been adjusted to apply to the new
.code-block-btnclass, enhancing user interaction by making the button visible when the code block is hovered over.
59-61: LGTM!The code changes are approved. A new class
.generate-btnhas been introduced, positioned to the right of the container, which suggests the addition of a new button functionality.
Line range hint
69-81: LGTM!The code changes are approved. The structure of the buttons has been refined, with the
.code-block-btnclass now having explicit cursor and positioning styles defined, enhancing its usability and visual consistency.packages/plugins/robot/src/js/useDialogContent.js (3)
26-28: LGTM!The code changes are approved. The introduction of the
copyButtonTextandgenerateButtonTextconstants improves code readability and maintainability by providing a single source of truth for the button text.
33-57: LGTM!The code changes are approved. The new instance of
ClipboardJSfor thegenerate-btnclass enhances the user experience by providing immediate feedback for generating schemas through a notification.
66-66: LGTM!The code changes are approved. The copy button text is now updated to "已复制" upon a successful copy action, maintaining the same timeout behavior for reverting the text and providing consistent user feedback.
packages/plugins/robot/src/Main.vue (1)
192-276: LGTM!The code changes are approved. The new
codeRulesconstant shifts the focus to generating a frontend page based on a JSON schema template. This change reflects a substantial shift in the functionality and purpose of thecodeRules, enhancing the code generation process to be more structured and aligned with contemporary practices.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- packages/plugins/robot/src/Main.vue (10 hunks)
Additional comments not posted (3)
packages/plugins/robot/src/Main.vue (3)
27-28: LGTM!The code changes are approved.
459-459: LGTM!The code changes are approved.
192-266: The newcodeRulestemplate looks good!The updated
codeRulestemplate follows a well-structured JSON schema format and adheres to modern frontend development best practices. The changes align with the provided list of alterations.To ensure the new
codeRulestemplate is being used correctly, run the following script:Verification successful
The
codeRulestemplate is used correctly in the codebase.The
codeRulesvariable is defined and utilized withinpackages/plugins/robot/src/Main.vueto construct messages, indicating that the new JSON schema template is being applied as intended. No issues were found with its usage.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of the new `codeRules` template in the codebase. # Test: Search for the usage of the new `codeRules` template. # Expect: The new template structure should be used when generating frontend pages. rg --type vue $'createNewPage\(schema\.schema\)' -A 10Length of output: 83
Script:
#!/bin/bash # Description: Search for the usage of the `codeRules` variable in the codebase. # Test: Search for the `codeRules` variable to verify its usage. rg 'codeRules' -A 10Length of output: 1457
|
@Fleurxxx 描述要认真写 |
Fleurxxx
force-pushed
the
ospp-2024/feat-schema-render
branch
from
fd8be59 to
da36ae8
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (4)
- packages/plugins/robot/src/ContentDialog.vue (1 hunks)
- packages/plugins/robot/src/Main.vue (17 hunks)
- packages/plugins/robot/src/js/robotSetting.js (1 hunks)
- packages/plugins/robot/src/js/useDialogContent.js (1 hunks)
Files skipped from review as they are similar to previous changes (2)
- packages/plugins/robot/src/ContentDialog.vue
- packages/plugins/robot/src/js/useDialogContent.js
Additional comments not posted (2)
packages/plugins/robot/src/js/robotSetting.js (1)
20-23: Verify the impact of AI model changes.The changes to the
AIModelOptionsarray involve removing two models and adding a new one. Ensure that all parts of the application that interact with these models are updated accordingly. Additionally, verify that the newmodelKeyis properly configured and used where necessary.packages/plugins/robot/src/Main.vue (1)
192-254: Approve the newcodeRulesimplementation.The changes to the
codeRulesconstant significantly enhance the structure and clarity of the code generation process. Ensure that the new rules are correctly integrated and functioning as expected within the application.Verification successful
Integration of
codeRulesis verified and correct.The
codeRulesconstant is defined and used within theMain.vuefile to construct a message or content block. The integration appears to be straightforward and correct, with no issues found in its usage.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the integration of the new `codeRules` in the application. # Test: Search for the usage of the new `codeRules` in the application. Expect: Proper integration and usage. rg --type vue -A 5 $'codeRules'Length of output: 58
Script:
#!/bin/bash # Description: Search for the usage of the `codeRules` constant in the entire codebase. # Test: Search for the usage of the `codeRules` constant. Expect: Proper integration and usage. rg -A 5 'codeRules'Length of output: 861
Fleurxxx
force-pushed
the
ospp-2024/feat-schema-render
branch
from
da36ae8 to
7e18101
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (4)
- packages/plugins/robot/src/ContentDialog.vue (1 hunks)
- packages/plugins/robot/src/Main.vue (17 hunks)
- packages/plugins/robot/src/js/robotSetting.js (1 hunks)
- packages/plugins/robot/src/js/useDialogContent.js (1 hunks)
Files skipped from review as they are similar to previous changes (3)
- packages/plugins/robot/src/ContentDialog.vue
- packages/plugins/robot/src/js/robotSetting.js
- packages/plugins/robot/src/js/useDialogContent.js
Additional comments not posted (3)
packages/plugins/robot/src/Main.vue (3)
Line range hint
1-91: Template Section Review: Well-structured and interactive.The template section is well-structured with proper use of Vue components and event handling. The dynamic bindings are correctly implemented, and the UI elements are appropriately configured for interactivity.
145-145: Script Section Review: Significant changes and improvements.
Current Model Handling:
The handling ofcurrentModelhas been updated to ensure it reflects the selected model accurately. This change is crucial for maintaining consistency in the application's state and user experience.Code Rules Update:
ThecodeRulesconstant has been significantly modified to focus on generating frontend pages from JSON schema templates. This change aligns with modern frontend development practices and enhances the application's functionality.Error Handling Improvement:
The addition of error handling in thesendRequestfunction improves the robustness of the application by managing token-related issues effectively.Model Switching Logic:
The logic for switching AI models has been refined to ensure that the current session is appropriately handled, preventing data loss and ensuring a smooth user experience.Model Selection Watcher:
The watcher forselectedModelhas been implemented to updatecurrentModeland manage token visibility based on the model's availability. This is a critical update for maintaining the integrity of user sessions.Also applies to: 162-164, 192-254, 304-304, 391-391, 441-447, 454-463
Line range hint
512-673: Style Section Review: Consistent and thematic.The style section is consistent with the application's design guidelines. The CSS rules are scoped properly, ensuring that they do not leak to other components. The use of variables for colors and dimensions enhances maintainability and theming capabilities.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- packages/plugins/robot/src/Main.vue (20 hunks)
Additional comments not posted (3)
packages/plugins/robot/src/Main.vue (3)
Line range hint
1-91: Review of Vue Template Structure and FunctionalityThe template section is well-structured with appropriate use of Vue components and directives. Event handling and data binding are correctly implemented, ensuring interactive and dynamic UI behavior. The use of scoped slots and dynamic classes enhances the flexibility and reusability of the UI components.
Line range hint
465-626: Review of Scoped CSS and Styling ConsistencyThe scoped CSS in the style section is well-organized and adheres to the project's design guidelines. The use of CSS variables for theming and responsive design considerations (like hover states and media queries) enhances the user experience and maintains consistency across different device sizes.
Line range hint
108-451: Review of Script Logic and Changes tocodeRulesThe script section effectively utilizes Vue's composition API, demonstrating good practices in reactive state management and component lifecycle handling. The significant changes to the
codeRulesconstant align with the PR's objectives to enhance schema rendering capabilities. This shift towards a more structured and template-driven approach for frontend development is commendable.However, ensure that all dependent components and services are updated to align with the new
codeRulesstructure to prevent any integration issues.Verification successful
codeRulesUsage is Localized toMain.vueThe
codeRulesconstant is defined and used exclusively within theMain.vuefile. It is utilized in thegetSendSeesionProcessfunction to modify message content. There are no other references tocodeRulesin the codebase, indicating that its changes are localized and do not impact other components or services.
- File:
packages/plugins/robot/src/Main.vue- Function:
getSendSeesionProcessScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that all dependent components and services are updated to align with the new `codeRules` structure. # Test: Search for the usage of `codeRules`. Expect: Updated usage in all relevant parts of the project. rg --type vue -A 5 $'codeRules'Length of output: 58
Script:
#!/bin/bash # Description: Verify that all dependent components and services are updated to align with the new `codeRules` structure. # Test: Search for the usage of `codeRules` across the codebase without specifying a file type. rg 'codeRules' -A 10Length of output: 1640
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
packages/plugins/robot/src/TokenDialog.vue (2)
65-71: Improved error handling, but consider additional enhancements.The introduction of a try-catch block for error handling is a good improvement. It ensures that the component can gracefully handle potential errors when setting the token in localStorage.
However, consider the following suggestions:
- Log the error for debugging purposes.
- Evaluate if localStorage is the most appropriate storage method for potentially sensitive token data.
Consider modifying the code as follows:
try { localStorage.setItem(props.currentModel.modelKey, keyForm.value.token) emit('token-status', true) closeKeyFormDialog() } catch (error) { + console.error('Failed to store token:', error) emit('token-status', false) }Additionally, consider using a more secure storage method for tokens, such as HttpOnly cookies or a dedicated secure storage solution, depending on your security requirements.
Line range hint
1-122: Overall assessment: Improvements made with room for further enhancements.The changes in this file have improved error handling and UI readability. The introduction of try-catch for error handling in the
submitKeyFormfunction is a positive step. However, consider implementing the suggested improvements:
- Add error logging for better debugging capabilities.
- Evaluate the security of using localStorage for token storage and consider more secure alternatives if necessary.
These enhancements will further improve the robustness and security of the component.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- packages/plugins/robot/src/Main.vue (20 hunks)
- packages/plugins/robot/src/TokenDialog.vue (2 hunks)
🔇 Additional comments (12)
packages/plugins/robot/src/TokenDialog.vue (1)
103-103: Improved readability in Chinese text.The addition of a space between "开启" and "AI" in the description string enhances readability. This is a good attention to detail that improves the user interface.
packages/plugins/robot/src/Main.vue (11)
118-118: LGTM: Import statement updated.The import statement has been updated to include
useLayoutfrom@opentiny/tiny-engine-controller. This is a good practice to keep all related imports together.
155-155: Variable renamed for consistency.The variable
inProcesinghas been renamed toinProcessing, fixing a typo and improving code consistency.
199-204: Update to page creation logic.The
createNewPagefunction has been updated to reset thepageStatus.datawhen creating a new page. This ensures a clean slate for each new page creation.
210-220: Code rules updated for clarity.The code rules have been updated to provide more specific guidelines for generating front-end code. This includes emphasizing the use of Vue 3 and TinyVue components, and specifying naming conventions.
Line range hint
248-264: Schema handling logic updated.The
sendRequestfunction has been updated to handle theschemaproperty in the response. If a schema is present, it callscreateNewPagewith the schema. This improves the component's ability to handle AI-generated page schemas.
278-278: Error handling improved.The
inProcessingflag is now set tofalsein the error handling block. This ensures that the processing state is correctly reset even when an error occurs.
Line range hint
400-416: Input validation and error handling improved.The
sendContentfunction now checks if processing is already in progress and notifies the user if so. This prevents multiple simultaneous requests and improves user experience.
428-428: Image content reset added.The
imageContentis now reset after sending the content. This ensures that old image data isn't accidentally reused in subsequent requests.
Line range hint
438-452: AI model initialization logic added.A new function
initCurrentModelhas been added to initialize the AI model based on the stored session data. This improves the consistency of the AI model selection across sessions.
569-574: Style improvements applied.Various style improvements have been made throughout the component, including:
- Adjustments to image dimensions and borders
- Updates to chat window layout and appearance
- Refinements to button and input styles
- Improvements to the chat model popover appearance
These changes enhance the overall visual consistency and user experience of the component.
Also applies to: 633-638, 644-665, 674-679, 694-726, 732-772, 778-798, 804-809
Line range hint
1-809: Overall improvements to the Main.vue component.The changes in this file encompass various improvements to the
Main.vuecomponent:
- Enhanced AI model handling and initialization
- Improved error handling and state management
- Updated code generation rules for better clarity
- Refined styling for better visual consistency and user experience
These changes collectively enhance the functionality, reliability, and appearance of the component. Great work on these improvements!
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (5)
packages/plugins/robot/docs/README.md (5)
1-5: Enhance the "Opening AI Chat Window" section with more details.While the section title is clear, it would be beneficial to provide step-by-step instructions on how to open the AI chat window. Additionally, consider adding alt text to the image for accessibility purposes.
Consider adding the following:
- Specific steps to open the chat window (e.g., "Click on the 'AI Chat' button in the top right corner").
- Alt text for the image:
- A brief description of what users should expect to see when the window opens.
6-24: LGTM! Comprehensive instructions for AI access token configuration.The section provides clear and detailed instructions for obtaining and inputting the AI access token. The emphasis on security and the step-by-step guide for generating the token from the Moonshot AI platform are particularly helpful.
Consider these minor enhancements:
- Add alt text to the images for improved accessibility.
- Include a note about the importance of keeping the access token confidential and not sharing it with others.
- Mention any token expiration policies or renewal processes, if applicable.
26-31: Expand on the page generation process and features.While the section provides a basic overview of generating pages using AI, it could benefit from more detailed instructions and explanations.
Consider adding:
- Step-by-step instructions for uploading images and providing descriptions.
- More information about the voice input feature, including how to activate and use it.
- Examples of the types of descriptions that work well for generating pages.
- Alt text for the image:
- A brief explanation of what users can expect in terms of the AI's capabilities and limitations in page generation.
33-35: Elaborate on the iterative design process using AI.The concept of modifying generated pages through continued interaction with the AI is powerful, but this section could benefit from more detailed explanations and examples.
Consider enhancing this section by:
- Providing examples of the types of questions or instructions users can give to modify pages.
- Explaining how the AI interprets and implements changes based on user input.
- Adding a simple example scenario of an iterative design process (e.g., changing colors, layouts, or adding new elements).
- Including tips on how to phrase requests effectively for optimal results.
- Mentioning any limitations in the modification process that users should be aware of.
1-35: Overall, a well-structured and informative user guide with room for enhancements.The README provides a good introduction to using the AI chat interface for web page generation. The structure is logical, and the inclusion of images is helpful. However, there are opportunities to enhance the document further.
Consider the following improvements:
- Add a table of contents at the beginning of the document for easy navigation.
- Include a section on troubleshooting common issues or frequently asked questions.
- Provide more examples throughout the document to illustrate key concepts.
- Add a section on best practices for effective interaction with the AI.
- Include information about any limitations or known issues with the AI page generation process.
- Consider adding version information or a last updated date to help users know if they're reading the most current documentation.
- If applicable, include links to additional resources or more detailed documentation.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (4)
packages/plugins/robot/docs/image/key_process1.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/key_process2.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/robot_process2.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/robot_process3.pngis excluded by!**/*.png
📒 Files selected for processing (2)
- packages/plugins/robot/docs/README.md (1 hunks)
- packages/plugins/robot/src/js/useDialogContent.js (1 hunks)
Fleurxxx
force-pushed
the
ospp-2024/feat-schema-render
branch
from
a2e07d4 to
07ec079
Compare
There was a problem hiding this comment.
Actionable comments posted: 9
🧹 Outside diff range and nitpick comments (3)
packages/plugins/robot/src/js/robotSetting.js (2)
20-23: LGTM! Consider adding English translations for comments.The changes to the
AIModelOptionsarray reflect an update in the available AI models, which aligns with the PR objectives. The addition of themodelKeyfor the new Kimi model is a good improvement.Consider adding English translations alongside the Chinese comments for better international collaboration:
- // 暂时不能使用，预留模型信息 + // 暂时不能使用，预留模型信息 (Temporarily unavailable, model information reserved)
Line range hint
79-81: Improve error handling ininitBlockListfunction.While catching errors is good practice, the current implementation might lead to silent failures. Consider adding proper error handling or at least logging the error for debugging purposes.
Suggested improvement:
} catch (err) { - // 捕获错误 + console.error('Failed to initialize block list:', err); + // TODO: Implement proper error handling (e.g., user notification) }packages/plugins/robot/src/TokenDialog.vue (1)
32-33: Align the error message with the validation logic for token lengthThe validation allows tokens with a length of up to 100 characters (
value.length > 100), but the error message says "请输入小于100位的...," which means "please enter less than 100 characters...". This discrepancy might confuse users.Consider updating the error message to reflect the validation logic:
callback(new Error('参数错误，请输入小于或等于100位的英文、数字、连字符或点号的字符串'))Alternatively, adjust the validation condition if the maximum length should be 99 characters:
- if (value.length > 100 || !tokenReg.test(value)) { + if (value.length >= 100 || !tokenReg.test(value)) {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (5)
packages/plugins/robot/docs/image/key_process1.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/key_process2.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/robot_process1.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/robot_process2.pngis excluded by!**/*.pngpackages/plugins/robot/docs/image/robot_process3.pngis excluded by!**/*.png
📒 Files selected for processing (8)
- .github/auto-labeler.yml (1 hunks)
- .github/workflows/auto-labeler.yml (1 hunks)
- packages/plugins/robot/docs/README.md (1 hunks)
- packages/plugins/robot/src/ContentDialog.vue (1 hunks)
- packages/plugins/robot/src/Main.vue (25 hunks)
- packages/plugins/robot/src/TokenDialog.vue (4 hunks)
- packages/plugins/robot/src/js/robotSetting.js (1 hunks)
- packages/plugins/robot/src/js/useDialogContent.js (1 hunks)
✅ Files skipped from review due to trivial changes (2)
- .github/auto-labeler.yml
- .github/workflows/auto-labeler.yml
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/plugins/robot/docs/README.md
- packages/plugins/robot/src/js/useDialogContent.js
🧰 Additional context used
🔇 Additional comments (7)
packages/plugins/robot/src/ContentDialog.vue (5)
48-49: Improved code readabilityThe addition of empty lines between style rules enhances the overall readability of the CSS code.
63-68: Refined copy button stylingThe modifications to the
.copy-btnclass improve the button's appearance and positioning. The addition of a fixed width ensures consistency, and the slight adjustment in positioning likely improves alignment with other elements.
49-53: Improved hover effect for code block buttonThe new hover effect with smooth transitions enhances the user experience. However, ensure that the class name change from
.copy-btnto.code-block-btnis consistent across the codebase.Run the following script to verify the class name usage:
#!/bin/bash # Description: Verify the usage of .code-block-btn class and check for any remaining .copy-btn classes # Test 1: Search for .code-block-btn usage echo "Searching for .code-block-btn usage:" rg -g '!*.md' '\bcode-block-btn\b' # Test 2: Search for any remaining .copy-btn usage echo "Searching for any remaining .copy-btn usage:" rg -g '!*.md' '\bcopy-btn\b'
Line range hint
69-81: Comprehensive styling for code block buttonThe new
.code-block-btnclass provides detailed and complete styling for the button, including hover effects and transitions. This enhances the overall look and feel of the UI.Please ensure that this new button styling integrates well with the existing layout, especially considering the different positioning approach (top vs. right).
Run the following script to verify the usage and potential conflicts:
#!/bin/bash # Description: Verify the usage of .code-block-btn and potential conflicts with .copy-btn # Test 1: Search for .code-block-btn usage in HTML/Vue templates echo "Searching for .code-block-btn usage in HTML/Vue templates:" rg -g '*.vue' -g '*.html' '\bcode-block-btn\b' # Test 2: Search for potential conflicts between .code-block-btn and .copy-btn echo "Searching for potential conflicts between .code-block-btn and .copy-btn:" rg -g '*.vue' -g '*.html' '(code-block-btn|copy-btn)'
58-62: New generate button style addedA new
.generate-btnclass has been introduced, suggesting the addition of a new button in the UI. The positioning indicates it's placed to the left of another button.Could you provide more information about the purpose and usage of this new generate button? Also, please ensure that the corresponding HTML and JavaScript for this button are implemented.
Run the following script to verify the usage of the new button:
packages/plugins/robot/src/js/robotSetting.js (1)
Line range hint
1-81: Overall, the changes look good with room for minor improvements.The updates to the
AIModelOptionsarray align well with the PR objectives of enhancing schema rendering capabilities. The addition of the new Kimi model and themodelKeyproperty is a positive change.Consider the following suggestions for further improvement:
- Add English translations for Chinese comments to enhance international collaboration.
- Implement proper error handling in the
initBlockListfunction to avoid silent failures.These minor adjustments will enhance the overall quality and maintainability of the code.
packages/plugins/robot/src/TokenDialog.vue (1)
66-66:⚠️ Potential issueVerify that
props.currentModel.modelKeyis defined before using itWhen storing the token in
localStorage, the keyprops.currentModel.modelKeymight beundefinedifmodelKeyis not set oncurrentModel. This could lead to unexpected behavior or errors.Consider adding a check to ensure
modelKeyexists:try { + if (!props.currentModel.modelKey) { + throw new Error('Model key is undefined') + } localStorage.setItem(props.currentModel.modelKey, keyForm.value.token) emit('token-status', true) closeKeyFormDialog() } catch (error) { emit('token-status', false) }Additionally, verify that all instances of
modelKeyare properly defined. You can run the following script to check forcurrentModelobjects without amodelKey:
|
@hexqi 老师在现在全部签名了 |
@hexqi Teacher has signed all of them now |
…urxxx/tiny-engine into ospp-2024/feat-schema-render
English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Background and solution
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
Release Notes
New Features
Improvements
Bug Fixes