Skip to content

Conversation

@kzhrk
Copy link

@kzhrk kzhrk commented Nov 8, 2025

Closes #2949

Extends the ignorePattern option to support CallExpression (function call)
patterns like $sanitize(test), previously only supporting simple identifiers.

This allows users to ignore sanitized HTML expressions using patterns such as
^\$sanitize\(.

@changeset-bot
Copy link

changeset-bot bot commented Nov 8, 2025

🦋 Changeset detected

Latest commit: b9ebc7e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
eslint-plugin-vue Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@kzhrk kzhrk marked this pull request as draft November 8, 2025 06:07
…uejs#2949)

This commit extends the `ignorePattern` option to support function call expressions
like `$sanitize(test)`, not just simple variable identifiers like `htmlSafe`.

Changes:
- Add new `shouldIgnore()` helper function that handles both Identifier and
  CallExpression expression types
- For Identifiers, use the `name` property directly for optimal performance
- For CallExpressions and other expression types, use `sourceCode.getText()`
  to get the full expression text
- Update the visitor to pass `sourceCode` to the new helper function

This allows users to configure patterns like `^\$sanitize\(` to match function
call expressions where the function name matches the pattern.

Tests:
- Add test case for CallExpression matching with ignorePattern `^\$sanitize\(`
- All existing tests continue to pass
@kzhrk kzhrk marked this pull request as ready for review November 8, 2025 06:14
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.

vue/no-v-html ignorePattern regex escaping causes different behavior in VS Code vs CLI

1 participant