-
Notifications
You must be signed in to change notification settings - Fork 745
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
Avoid treating warnings as errors inside the IDE #2727
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've sort of wanted to do this, especially after @OmicronPersei wanted to write the XML docs last instead of first.
<PropertyGroup Condition="'$(BuildingInsideVisualStudio)' != 'true'"> | ||
<!-- Ideally this is always enabled, but that tends to hurt developer productivity --> | ||
<TreatWarningsAsErrors>true</TreatWarningsAsErrors> | ||
</PropertyGroup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My preference would have been to wait until two properties shared the condition before adding a new property group:
<Features>strict</Features>
+
+ <!-- Ideally this is always enabled, but that tends to hurt developer productivity -->
+ <TreatWarningsAsErrors Condition="'$(BuildingInsideVisualStudio)' != 'true'">true</TreatWarningsAsErrors>
+
<SignAssembly>true</SignAssembly>
But not important.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to treat this like a functional unit, which can be copied to other projects as needed. I'll move it if you want me to move it; let me know the decision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no problem with it, just curiosity!
AppVeyor timed out executing the tests. I've restarted it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I don't feel strongly for whether it should be a new property group or just a single element. I'll leave the decision for @jnm2.
Thanks Sam! |
This change helps improve developer inner loop efficiency by revealing but not demanding attention for warnings that occur during normal iterative development. Anything missed will still be caught by the CI and command line builds.
💡 Please do not rebase or squash this pull request on merge.