fix: disallow extra properties in rule options

[andreww2012]

The plugin rule currently allows extra properties to be passed in the second options object, which should not be allowed because they're not used by the rule, and this only makes it easier for typos in rule options to go unnoticed.

This PR simply disallows extra properties in this rule's schema.

---

Important

Disallows extra properties in the second options object of the prettier rule schema in eslint-plugin-prettier.js.

• Behavior:
  • Disallows extra properties in the second options object of the prettier rule schema in eslint-plugin-prettier.js.
  • Ensures only specified properties (usePrettierrc, fileInfoOptions) are allowed, preventing unnoticed typos.

^{This description was created by for 7aa6758. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• Refactor
  • Tightened validation for configuration options by restricting allowed properties for the prettier rule. Only explicitly defined options are now permitted; any extra properties will result in a validation error.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7aa6758

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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 update refines the JSON schema validation for the prettier rule options in the ESLint plugin configuration. The schema now disallows any properties other than usePrettierrc and fileInfoOptions in the second options object, enforcing stricter validation without affecting runtime logic or control flow.

Changes

File(s)	Change Summary
eslint-plugin-prettier.js	Tightened JSON schema for the prettier rule: set additionalProperties to false in the second options object, restricting allowed properties to usePrettierrc and fileInfoOptions.

Poem

In the warren of lint, we hop with care,
Schema now stricter—no extras to spare!
Only the named may burrow inside,
The rest must wait, or hop aside.
With tidy rules, our code will gleam—
Prettier than a bunny’s dream! 🐇✨

---

📜 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 3e87f2e and 7aa6758.

📒 Files selected for processing (1)

• eslint-plugin-prettier.js (1 hunks)

🔇 Additional comments (1)

eslint-plugin-prettier.js (1)

169-169: LGTM! This change improves rule option validation.

Setting additionalProperties: false correctly restricts the second options object to only the documented properties (usePrettierrc and fileInfoOptions). This will help catch typos and prevent unused options from being silently ignored, which aligns perfectly with the PR objective.

The runtime logic only uses these two properties anyway, so this schema tightening provides better developer experience without affecting functionality.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• 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>, 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.
  • @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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 7aa6758 in 1 minute and 0 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. eslint-plugin-prettier.js:169

• Draft comment:
  Setting 'additionalProperties' to false here enforces strict validation for the second options object, preventing unnoticed typos. Ensure that allowing extra properties in the nested 'fileInfoOptions' (line 164-167) is intentional.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

Workflow ID: wflow_GnEnsGcPuBrDPpsq

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/eslint-plugin-prettier@751

commit: 7aa6758