Skip to content

only report EXP0026 when the stub extensions are not in scope - #91

Open
koenbeuk wants to merge 1 commit into
mainfrom
fix/exp0026-false-positive
Open

only report EXP0026 when the stub extensions are not in scope#91
koenbeuk wants to merge 1 commit into
mainfrom
fix/exp0026-false-positive

Conversation

@koenbeuk

@koenbeuk koenbeuk commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI review requested due to automatic review settings August 2, 2026 01:17
@codecov

codecov Bot commented Aug 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR refines the MissingExpressiveImportAnalyzer (EXP0026) so it only reports when the ExpressiveSharp stub extension type isn’t actually in scope, avoiding false positives in cases where calls intentionally bind to System.Linq.Queryable (e.g., passing a pre-built Expression<Func<...>>).

Changes:

  • Update the analyzer to check whether ExpressiveQueryableLinqExtensions is in scope before reporting EXP0026.
  • Add a regression test ensuring no EXP0026 is reported when using ExpressiveSharp; is present and a pre-built expression tree is passed to Where.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
tests/ExpressiveSharp.Generator.Tests/CodeFixers/MissingExpressiveImportAnalyzerTests.cs Adds a regression test for the “pre-built expression tree + using present” scenario to prevent EXP0026 false positives.
src/ExpressiveSharp.CodeFixers/MissingExpressiveImportAnalyzer.cs Gates EXP0026 emission on whether the stub extension type is actually in scope at the call site.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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