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

Development: Add linting rule for dayjs #10282

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

az108
Copy link
Contributor

@az108 az108 commented Feb 6, 2025

Checklist

General

Motivation and Context

While working on this PR (#10269) , I accidentally imported dayjs without /esm. Since we want to avoid this, new developers who might not be aware of it should be informed.

Description

I added a restriction in the ESLint config to prevent importing dayjs directly and included a message kindly asking developers to import dayjs/esm instead. Now, if someone tries to push with dayjs as an import, it won’t be possible anymore.

Review Progress

Code Review

  • Code Review 1

Summary by CodeRabbit

  • Chores
    • Updated internal quality guidelines to enforce consistent module imports, enhancing overall stability and maintainability.
    • Strengthened development practices to mitigate potential issues without altering user-facing functionality.
    • This implementation reflects our ongoing efforts to refine the development process and ensure a robust, seamless experience for end-users.

@az108 az108 requested a review from a team as a code owner February 6, 2025 21:51
@az108 az108 self-assigned this Feb 6, 2025
@az108 az108 added this to the 7.10.0 milestone Feb 6, 2025
Copy link

coderabbitai bot commented Feb 6, 2025

Walkthrough

The change updates the ESLint configuration in eslint.config.mjs by adding a new rule. The new rule, 'no-restricted-imports', is configured to trigger an error when the module 'dayjs' is imported directly. Instead, it enforces importing from 'dayjs/esm'. This configuration change aims to ensure that the code adheres to a specific module structure during the linting process.

Changes

File Summary
eslint.config.mjs Added the 'no-restricted-imports' rule to disallow direct imports of 'dayjs' in favor of 'dayjs/esm'.

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc1e3cb and f821a6a.

📒 Files selected for processing (1)
  • eslint.config.mjs (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Call Build Workflow / Build .war artifact
  • GitHub Check: Call Build Workflow / Build and Push Docker Image
  • GitHub Check: client-tests
  • GitHub Check: server-tests
  • GitHub Check: Analyse
🔇 Additional comments (1)
eslint.config.mjs (1)

120-130: LGTM! The ESLint rule is well-configured.

The implementation effectively blocks direct imports of 'dayjs' and provides a clear message guiding developers to use 'dayjs/esm' instead.

Let's verify that the rule catches direct dayjs imports and allows the correct import path:

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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
🪧 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. (Beta)
  • @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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

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
Contributor

@Strohgelaender Strohgelaender left a comment

Choose a reason for hiding this comment

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

Good idea, thanks. Works locally.
grafik

@krusche krusche changed the title General: Add linting rule for dayjs Development: Add linting rule for dayjs Feb 7, 2025
@krusche krusche merged commit be59ece into develop Feb 7, 2025
27 of 34 checks passed
@krusche krusche deleted the chore/general/add-lint-for-usage-of-dayjs branch February 7, 2025 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Merged
Development

Successfully merging this pull request may close these issues.

3 participants