You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: