fix: Mock data is changed to be obtained from loginUserContext

[lu-yg]

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

• Bug Fixes
  • Updated the user profile retrieval to dynamically display your account details based on your login, replacing the previous static behavior.

[coderabbitai]

Walkthrough

The pull request introduces documentation enhancements and a control flow update across two controller classes. In the CanvasController, a JavaDoc comment is added for the canvasService field. In the UserController, a new loginUserContext dependency is injected and documented. The me method in UserController is updated to dynamically retrieve the user ID from loginUserContext instead of using a hardcoded value.

Changes

File(s)	Change Summary
base/.../CanvasController.java	Added JavaDoc comment for the canvasService field.
base/.../UserController.java	Added loginUserContext field with @Autowired annotation and updated the me method to use a dynamic user ID from loginUserContext instead of a hardcoded value.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant UserController
    participant LoginUserContext
    participant UserService

    Client->>UserController: Request "me"
    UserController->>LoginUserContext: getLoginUserId()
    LoginUserContext-->>UserController: loginUserId
    UserController->>UserService: queryUserById(loginUserId)
    UserService-->>UserController: user data
    UserController-->>Client: return user data

Loading

Poem

Oh, what a hop, a joyful trance,
Code improved by careful glance,
A comment here, a dependency there,
User ID now floats in the air!
With carrots and codes, I cheer and prance. 🥕🐰
A rabbit's delight in every dance!

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

❤️ 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.
• @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]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b1370f0 and b70579e.

📒 Files selected for processing (2)

• base/src/main/java/com/tinyengine/it/controller/CanvasController.java (1 hunks)
• base/src/main/java/com/tinyengine/it/controller/UserController.java (2 hunks)

🔇 Additional comments (3)

base/src/main/java/com/tinyengine/it/controller/CanvasController.java (1)

44-46: Documentation improvement looks good.

Adding JavaDoc comments to the canvasService field improves code readability and maintainability. This follows good software development practices.

base/src/main/java/com/tinyengine/it/controller/UserController.java (2)

15-16: Import added correctly.

The import for LoginUserContext has been correctly added to support the new dependency.

---

46-50: Dependency injection and documentation look good.

The addition of the loginUserContext field with proper JavaDoc and @Autowired annotation follows the project's documentation pattern and dependency injection approach.