Skip to content

Release/v1.0.0 #224

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

Closed
wants to merge 2 commits into from
Closed

Release/v1.0.0 #224

wants to merge 2 commits into from

Conversation

lu-yg
Copy link
Collaborator

@lu-yg lu-yg commented May 21, 2025

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • 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
  • 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?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • New Features
    • Added support for associating a component library with an application through a new field.
  • Bug Fixes
    • Improved authorization checks to use the actual logged-in user for page deletion.
  • Tests
    • Updated tests to reflect new field handling in metadata operations.

Copy link

coderabbitai bot commented May 21, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

A new nullable integer column app_id was added to the t_component_library table in both H2 and MySQL schemas. The corresponding Java entity, MyBatis mapper, and related CRUD operations were updated to support this field. Additional logic ensures proper handling of user context and tenant ID in service and handler classes, with relevant tests adjusted.

Changes

File(s) Change Summary
app/src/main/resources/sql/h2/create_all_tables_ddl_v1.h2.sql
app/src/main/resources/sql/h2/update_all_tables_ddl.sql
app/src/main/resources/sql/mysql/create_all_tables_ddl_v1.mysql.sql
app/src/main/resources/sql/mysql/update_all_tables_ddl.sql
Added nullable integer column app_id to t_component_library table in both H2 and MySQL schemas.
base/src/main/java/com/tinyengine/it/model/entity/ComponentLibrary.java Added private Integer field appId with schema annotation to the ComponentLibrary entity.
base/src/main/resources/mappers/ComponentLibraryMapper.xml Integrated app_id/appId into all relevant CRUD operations, result mappings, and SQL fragments.
base/src/main/java/com/tinyengine/it/common/handler/MyMetaObjectHandler.java Modified insertFill to fill the tenantId field using the current login user context.
base/src/main/java/com/tinyengine/it/service/app/impl/PageServiceImpl.java Updated checkDelete to use the logged-in user's ID from context instead of a hardcoded value.
base/src/test/java/com/tinyengine/it/common/handler/MyMetaObjectHandlerTest.java Adjusted test to expect one additional call to hasSetter due to the new filled field.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Service
    participant Mapper
    participant Database

    User->>Service: Create/Update ComponentLibrary (with appId)
    Service->>Mapper: Map appId property
    Mapper->>Database: Insert/Update t_component_library (includes app_id)
    Database-->>Mapper: Confirm operation
    Mapper-->>Service: Return result
    Service-->>User: Operation result
Loading

Poem

A new field hops into view,
app_id joins the SQL crew!
Mappers and models, all in line,
CRUD and tests now intertwine.
With tenant and user handled right,
The schema’s future’s looking bright!
(🐇 Hopping forward, code in sight!)

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 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 bd015fe and 24dd8f6.

📒 Files selected for processing (9)
  • app/src/main/resources/sql/h2/create_all_tables_ddl_v1.h2.sql (1 hunks)
  • app/src/main/resources/sql/h2/update_all_tables_ddl.sql (1 hunks)
  • app/src/main/resources/sql/mysql/create_all_tables_ddl_v1.mysql.sql (1 hunks)
  • app/src/main/resources/sql/mysql/update_all_tables_ddl.sql (1 hunks)
  • base/src/main/java/com/tinyengine/it/common/handler/MyMetaObjectHandler.java (1 hunks)
  • base/src/main/java/com/tinyengine/it/model/entity/ComponentLibrary.java (1 hunks)
  • base/src/main/java/com/tinyengine/it/service/app/impl/PageServiceImpl.java (1 hunks)
  • base/src/main/resources/mappers/ComponentLibraryMapper.xml (8 hunks)
  • base/src/test/java/com/tinyengine/it/common/handler/MyMetaObjectHandlerTest.java (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch release/v1.0.0
  • Post Copyable Unit Tests in Comment

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.

❤️ Share
🪧 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 @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @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 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 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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this 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.

Copy link

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@lu-yg lu-yg closed this May 21, 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.

1 participant