Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log INFO level when source generated projects don't have valid GUIDs #1899

Open
andrei-epure-sonarsource opened this issue Apr 3, 2024 · 0 comments

Comments

@andrei-epure-sonarsource
Copy link
Contributor

andrei-epure-sonarsource commented Apr 3, 2024

See this community post.

Which is related to #1309

When we see that projects are outside the project base path and don't have valid guids, we should not log WARN level messages but just INFO. We can assume those projects are source-generated.

This can be an easy fix to reduce noise.

And we need to also fix #1309 because currently, the base path is computed wrongly for Azure Functions projects. We could even make a baby step to check the name of the project with invalid guid and if it's WorkerExtensions.csproj, to log INFO level, because we know this happens for Azure Functions projects.

And to fail in case the base project path is wrong for #1309 - as separate logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant