chore: update eslint configuration and adjust docker command

[anncwb]

Description

update eslint configuration and adjust docker command, close #4094

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

  • Enhanced Docker configuration by including nginx.conf for improved management of containerized applications.

• Improvements

  • Simplified the path for the Nginx configuration in the Dockerfile, streamlining project structure.

• Bug Fixes

  • Removed unnecessary commented-out configurations in nginx.conf to reduce confusion and improve clarity.

• Documentation

  • Updated ESLint configuration to relax certain linting rules for specific directories, accommodating existing code styles.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e4e3b8c

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]

Walkthrough

The recent changes enhance the project’s development environment by updating the Docker-related configurations and ESLint rules. The .vscode/settings.json now includes nginx.conf alongside the Dockerfile for better management of associated files. The Dockerfile references a simplified path for the Nginx configuration, and ESLint has relaxed rules for certain packages, promoting a more flexible coding style. Additionally, unused configurations in nginx.conf were removed, streamlining the setup.

Changes

File	Change Summary
.vscode/settings.json, Dockerfile	Updated Dockerfile paths and included nginx.conf in settings.
internal/lint-configs/eslint-config/src/...	Added rules to relax linting for specific directories.
nginx.conf	Removed commented-out stream module configuration for Redis, simplifying the file.

Poem

🌿 In a world of code where rabbits play,
Changes hop forth, brightening the day.
With Nginx set in a cozy new place,
ESLint's rules now allow more grace.
Oh, how we cheer with a joyful thump,
For cleaner configs, let’s all do a jump! 🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5b56c30 and e4e3b8c.

Files selected for processing (4)

• .vscode/settings.json (1 hunks)
• Dockerfile (1 hunks)
• internal/lint-configs/eslint-config/src/custom-config.ts (2 hunks)
• nginx.conf (1 hunks)

Files skipped from review due to trivial changes (2)

• Dockerfile
• nginx.conf

Additional comments not posted (3)

internal/lint-configs/eslint-config/src/custom-config.ts (2)

17-23: Disabling perfectionist/sort-interfaces for specific packages.

The perfectionist/sort-interfaces rule has been turned off for files in packages/effects and packages/types. This change might be intended to accommodate existing code styles or reduce friction during development. Ensure that this relaxation aligns with the team's coding standards and that any potential impacts on code consistency are considered.

---

56-56: Consistent rule application across configurations.

The perfectionist/sort-interfaces rule is consistently turned off across different sections of the configuration. This uniformity helps maintain consistency in how interfaces are handled throughout the codebase.

.vscode/settings.json (1)

186-186: Including nginx.conf in Docker-related file associations.

The addition of nginx.conf to the list of associated files for the "Dockerfile" key indicates an expanded scope for Docker-related operations. This change may reflect a shift in how the project manages or deploys its containerized applications, potentially improving configuration management.