Skip to content

chore: update ESLint configuration #22924

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

Merged
merged 2 commits into from
Aug 6, 2025
Merged

Conversation

zhyd1997
Copy link
Contributor

@zhyd1997 zhyd1997 commented Aug 6, 2025

What does this PR do?

Visual Demo (For contributors especially)

A visual demonstration is strongly recommended, for both the original and new change (video / image - any one).

Video Demo (if applicable):

  • Show screen recordings of the issue or feature.
  • Demonstrate how to reproduce the issue, the behavior before and after the change.

CleanShot 2025-08-06 at 22 08 05

Image Demo (if applicable):

  • Add side-by-side screenshots of the original and updated change.
  • Highlight any significant change(s).

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  • Are there environment variables that should be set?
  • What are the minimal test data to have?
  • What is expected (happy path) to have (input and output)?
  • Any other important info that could help to test that PR

Checklist

  • I haven't read the contributing guide
  • My code doesn't follow the style guidelines of this project
  • I haven't commented my code, particularly in hard-to-understand areas
  • I haven't checked if my changes generate no new warnings

Copy link

vercel bot commented Aug 6, 2025

@zhyd1997 is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Aug 6, 2025
@graphite-app graphite-app bot requested a review from a team August 6, 2025 14:10
Copy link
Contributor

coderabbitai bot commented Aug 6, 2025

Walkthrough

The ESLint configuration file .eslintrc.js was modified to export an object with an extends property pointing to the preset configuration file, instead of directly exporting the preset module. A JSDoc type annotation was added to specify the configuration type, and a comment was included to clarify the scope of the configuration. Additionally, a semicolon was added to a statement in apps/api/v1/pages/api/availability/_get.ts without affecting any logic or functionality.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix ESLint failure during local CI tasks (#22905)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c5e1fcc and 4aec18e.

📒 Files selected for processing (1)
  • apps/api/v1/pages/api/availability/_get.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • apps/api/v1/pages/api/availability/_get.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Install dependencies / Yarn install & cache
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
  • 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 explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this 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.

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.

@github-actions github-actions bot added ci area: CI, DX, pipeline, github actions 🐛 bug Something isn't working labels Aug 6, 2025
Copy link
Contributor

@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

🧹 Nitpick comments (1)
.eslintrc.js (1)

3-5: Add root: true to prevent parent config bleed-through
Without root: true, ESLint will continue walking up the directory tree and may pick up unexpected configs, re-introducing the CI inconsistencies this PR aims to fix.

 module.exports = {
+  root: true,
   extends: ["./packages/config/eslint-preset.js"],
 };
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b410316 and c5e1fcc.

📒 Files selected for processing (1)
  • .eslintrc.js (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
PR: calcom/cal.com#0
File: .cursor/rules/review.mdc:0-0
Timestamp: 2025-07-28T11:50:23.946Z
Learning: For large pull requests (>500 lines changed or >10 files touched), advise splitting into smaller, focused PRs by feature, layer, dependency chain, or file/module
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Install dependencies / Yarn install & cache
🔇 Additional comments (2)
.eslintrc.js (2)

2-2: Good JSDoc annotation
The explicit Linter.Config type improves IDE support and helps catch mis-typed fields early.


4-4: Double-check the preset path
The path now includes the .js extension. Verify that the file on disk matches (eslint-preset.js) and is referenced consistently across the repo; otherwise ESLint resolution will fail, especially if the preset was previously published as index.js, .cjs, etc.

Copy link
Contributor Author

@zhyd1997 zhyd1997 left a comment

Choose a reason for hiding this comment

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

Copy link

graphite-app bot commented Aug 6, 2025

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (08/06/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (08/06/25)

1 label was added to this PR based on Keith Williams's automation.

"Add ready-for-e2e label" took an action on this PR • (08/06/25)

1 label was added to this PR based on Keith Williams's automation.

zomars
zomars previously approved these changes Aug 6, 2025
Copy link
Member

@zomars zomars left a comment

Choose a reason for hiding this comment

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

Nice find! How did you stumble upon this solution? Nice work regardless

@zomars
Copy link
Member

zomars commented Aug 6, 2025

/tip 25

Copy link

algora-pbc bot commented Aug 6, 2025

Please visit Algora to complete your tip via Stripe.

@algora-pbc algora-pbc bot added the 💰 Rewarded Rewarded bounties on Algora.io label Aug 6, 2025
Copy link

algora-pbc bot commented Aug 6, 2025

🎉🎈 @zhyd1997 has been awarded $25 by Cal.com, Inc.! 🎈🎊

@zomars zomars enabled auto-merge (squash) August 6, 2025 17:01
Added a missing semicolon after the getUserAvailabilityService() call to maintain code consistency and prevent potential issues.
@zomars zomars requested review from a team as code owners August 6, 2025 17:21
@zomars zomars merged commit eda328d into calcom:main Aug 6, 2025
31 of 35 checks passed
Copy link
Contributor

github-actions bot commented Aug 6, 2025

E2E results are ready!

@zhyd1997
Copy link
Contributor Author

zhyd1997 commented Aug 6, 2025

Nice find! How did you stumble upon this solution? Nice work regardless

I just spent half an hour with ChatGPT, Codex, Copilot, Gemini 2.5 Pro, and Claude Code—and none of them made any sense.
So I decided to dig into the ESLint source code, and eventually found the troubleshooting docs mentioned above.
Since I’m also using a Turborepo with a .eslintrc.js at the root, I checked out this file: https://github.com/zhyd1997/velokit/blob/main/.eslintrc.js
I gave it a try—and it worked.

@zhyd1997 zhyd1997 deleted the build/22905-1754483131 branch August 6, 2025 21:34
Pallava-Joshi pushed a commit to Pallava-Joshi/cal.com that referenced this pull request Aug 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working ci area: CI, DX, pipeline, github actions community Created by Linear-GitHub Sync ready-for-e2e 💰 Rewarded Rewarded bounties on Algora.io
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ESline fails during local CI tasks
2 participants