fix: enablePreferences does not meet expectations

[anncwb]

Description

fixed #4029

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• New Features

  • Added a new preferences option in the user dropdown menu, which is conditionally displayed based on user settings.
  • Introduced a basic NGINX configuration for handling HTTP requests and enabling CORS.

• Chores

  • Updated the naming convention for the local Docker image.
  • Modified commit linting rules to allow more flexibility in commit message formats.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b6f9e7c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduced in this update enhance the functionality and usability of the application. Notably, the Docker image name has been simplified, a new NGINX configuration has been added for effective request handling, and the user dropdown component now dynamically displays preferences based on user settings. Additionally, commit linting rules have been adjusted to allow more flexibility in commit message formatting.

Changes

Files	Change Summary
build-local-docker-image.sh	Renamed IMAGE_NAME from "vben-admin-pro-local" to "vben-admin-local".
deploy/nginx.conf	Introduced basic NGINX configuration for handling HTTP requests, including CORS and error management.
internal/lint-configs/commitlint-config/index.mjs	Disabled the subject-case linting rule, allowing any case for commit subjects.
packages/effects/layouts/src/widgets/user-dropdown/user-dropdown.vue	Added conditional rendering for preferences option based on preferences.app.enablePreferences.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Dropdown
    participant Preferences

    User->>Dropdown: Click User Dropdown
    Dropdown->>Preferences: Check preferences.app.enablePreferences
    alt Preferences Enabled
        Dropdown->>User: Show Preferences Option
    else Preferences Disabled
        Dropdown->>User: Hide Preferences Option
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Component hides preferences when preferences.app.enablePreferences=false (#[4029])	✅
Ensure user experience is enhanced by dynamic rendering of options (#[4029])	✅

Poem

🐰 In fields of code where changes bloom,
A dropdown dances, dispelling gloom.
With Docker's name now light and bright,
NGINX stands guard, ready to fight.
So let us hop with joy and cheer,
For flexible commits and preferences near! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.