Skip to content
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

chore: link to internal eslint plugin #462

Merged
merged 1 commit into from
Apr 6, 2024

Conversation

aversini
Copy link
Collaborator

@aversini aversini commented Apr 6, 2024

Summary by CodeRabbit

  • Chores
    • Updated the project's dependency management for improved internal consistency.

Copy link

coderabbitai bot commented Apr 6, 2024

Walkthrough

This update involves adjusting the project's dependency management by changing the reference for @versini/eslint-plugin-client in the package.json file. Instead of pointing to a specific version of the package, it now uses a workspace reference to link directly to the local package located at ./packages/eslint-plugin-client. This change facilitates easier development and testing of the ESLint plugin within the same workspace.

Changes

File(s) Change Summary
package.json Modified dependency @versini/eslint-plugin-client to use workspace reference ./packages/eslint-plugin-client.

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration 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/coderabbit-overrides.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

github-actions bot commented Apr 6, 2024

Bundle Size (components)

Status File Size (Gzip) Limits
style.css 6.91 KB 8 KB
index.js 8.26 KB (-1 B -0.01%) 20 KB
vendor.js 65.07 KB 67 KB

Overall bundle size: 80.24 KB (-1 B 0.00%)
Overall status: ✅

Bundle Size (form components)

Status File Size (Gzip) Limits
index.js 4.73 KB (+2 B +0.04%) 20 KB
vendor.js 44.49 KB 67 KB

Overall bundle size: 49.22 KB (+2 B 0.00%)
Overall status: ✅

Bundle Size (system)

Status File Size (Gzip) Limits
style.css 7.25 KB 8 KB
index.js 1.74 KB (+1 B +0.06%) 3 KB
vendor.js 44.49 KB 46 KB

Overall bundle size: 53.48 KB (+1 B 0.00%)
Overall status: ✅

@aversini aversini merged commit 636e5a8 into main Apr 6, 2024
5 checks passed
@aversini aversini deleted the chore-link-to-internal-eslint-plugin branch April 6, 2024 14:22
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Status

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between 60d2955 and ce46114.
Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (1)
package.json (1)

20-20: The change to reference @versini/eslint-plugin-client as a workspace dependency is a good practice for monorepo setups, ensuring easier management and updates of the ESLint plugin.

Ensure that the path ./packages/eslint-plugin-client correctly points to the ESLint plugin within the workspace. Additionally, verify that all linting scripts and configurations are updated to reflect this change.

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