Skip to content

Comments

docs(linter): clarify fixWith vs suggest in no-restricted-types rule#16277

Closed
Copilot wants to merge 2 commits intoc/11-29-feat_linter_add_tsanykeyword_support_to_no-restricted-types_rulefrom
copilot/sub-pr-16276
Closed

docs(linter): clarify fixWith vs suggest in no-restricted-types rule#16277
Copilot wants to merge 2 commits intoc/11-29-feat_linter_add_tsanykeyword_support_to_no-restricted-types_rulefrom
copilot/sub-pr-16276

Conversation

Copy link
Contributor

Copilot AI commented Nov 29, 2025

Addresses review feedback to document the distinction between fixWith and suggest options.

  • fixWith: Automatic fix applied with --fix. Use for safe, deterministic replacements (e.g., Stringstring)
  • suggest: Manual review suggestion shown in editors. Use when human judgment needed (e.g., ObjectRecord<string, unknown>)
  • Added field-level docs and noted fixWith takes precedence when both specified
{
  "types": {
    "String": { "message": "Use primitive", "fixWith": "string" },
    "Object": { "message": "Be specific", "suggest": ["Record<string, unknown>", "object"] }
  }
}

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Address documentation improvements based on review feedback docs(linter): clarify fixWith vs suggest in no-restricted-types rule Nov 29, 2025
Copilot AI requested a review from camc314 November 29, 2025 17:03
@camc314 camc314 closed this Nov 29, 2025
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.

2 participants