Change FunctionNotFound analyzer severity to Info for cross-assembly scenarios #584
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…#580 Co-authored-by: YunchuWang <[email protected]>
Copilot
AI
changed the title
[WIP] Update functionnotfound analyzer severity level to info
Change FunctionNotFound analyzer severity to Info for cross-assembly scenarios
Dec 19, 2025
YunchuWang
approved these changes
Dec 19, 2025
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses false positives in the FunctionNotFoundAnalyzer (DURABLE2003/DURABLE2004) by downgrading their severity from Warning to Info and clarifying that cross-assembly function references cannot be validated at compile time.
Key Changes:
- Severity changed from
DiagnosticSeverity.WarningtoDiagnosticSeverity.Infofor both DURABLE2003 and DURABLE2004 - Diagnostic messages updated to clarify that cross-assembly functions are not statically resolvable
- Documentation updated to use "Reports" instead of "Warns" to reflect the Info severity level
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/Analyzers/Activities/FunctionNotFoundAnalyzer.cs |
Updated severity from Warning to Info for both ActivityNotFoundRule and SubOrchestrationNotFoundRule |
src/Analyzers/Resources.resx |
Added clarification text to diagnostic messages explaining that cross-assembly functions can be safely ignored |
src/Analyzers/AnalyzerReleases.Shipped.md |
Updated documentation to reflect Info severity and changed "Warns" to "Reports" with added cross-assembly explanation |
halspang
approved these changes
Dec 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DURABLE2003/DURABLE2004 analyzers report false positives when activity functions or sub-orchestrations are defined in referenced assemblies, since Roslyn analyzers cannot resolve symbols across assembly boundaries at compile time.
Changes
WarningtoInfofor both DURABLE2003 (activity) and DURABLE2004 (sub-orchestration)AnalyzerReleases.Shipped.mdto reflect severity changeExample diagnostic output
Before:
After:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.